[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C1T5P92M2D9KEW68N0JEMC":3,"skill-same:01M6C1T5P92M2D9KEW68N0JEMC":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":14,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M6C1T5P92M2D9KEW68N0JEMC","knowledge-management",null,"Create or update knowledge files for a feature area. Use when the user says \"update knowledge\", \"create knowledge file for X\", \"document this feature\", or after completing a feature that needs knowledge documentation.","cartaorobbin\u002Fpyramid-temporal","cartaorobbin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F133803757?v=4","01M6C1SVA1FFVXFG0QTK8ZRNDV","robbin Pagamentos","01M6C1SVEDYW8ZDTP82V7DF2BQ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fknowledge-management\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32],"knowledge","management","knowledge management","documentation","create","update","file","user","use","2026-11-10 10:12:30",false,"---\nname: knowledge-management\ndescription: Create or update knowledge files for a feature area. Use when the user says \"update knowledge\", \"create knowledge file for X\", \"document this feature\", or after completing a feature that needs knowledge documentation.\n---\n\n# Knowledge Management\n\nThis skill guides you through creating or updating files in the `knowledge\u002F` directory. Follow the conventions defined in `.cursor\u002Frules\u002Fknowledge.mdc`.\n\n## Step 1: Determine the Action\n\nUse AskQuestion:\n\n```\nprompt: \"What would you like to do?\"\noptions:\n  - Create a new knowledge file for a feature area\n  - Update an existing knowledge file\n  - Review all knowledge files for staleness\n```\n\n---\n\n## Creating a New Knowledge File\n\n### Step 2a: Identify the Feature Area\n\nAsk the user which feature area to document, or infer it from the conversation context. The file should be named after the feature area in lowercase with underscores (e.g., `knowledge\u002Fbilling.md`, `knowledge\u002Fauth.md`).\n\n### Step 3a: Explore the Codebase\n\nRead the source code for the feature area thoroughly:\n1. Identify the key modules, classes, and functions\n2. Trace the main code paths and data flow\n3. Note design decisions that are not obvious from the code alone\n4. Look for edge cases, gotchas, and non-obvious behaviors\n\nAlso read `knowledge\u002Farchitecture.md` to understand how this area fits into the overall system.\n\n### Step 4a: Draft the Knowledge File\n\nWrite the file following this structure:\n\n```markdown\n# \u003CFeature Area Name>\n\n\u003COne or two sentences describing what this area does.>\n\n## Design Decisions\n\n\u003CWhy it works the way it does. Trade-offs, constraints, alternatives considered. Use a heading per decision if there are several.>\n\n## API Surface\n\n\u003CKey classes, functions, types, and their relationships. Focus on what another developer (or the AI) needs to know to work in this area correctly.>\n\n## Key Learnings \u002F Gotchas\n\n\u003CNon-obvious behaviors, edge cases, things that broke before, common mistakes to avoid.>\n```\n\n### Step 5a: Write and Confirm\n\nWrite the file to `knowledge\u002F\u003Cfeature-area>.md`. Tell the user what was created and suggest they review it.\n\n---\n\n## Updating an Existing Knowledge File\n\n### Step 2b: Identify What Changed\n\nDetermine which knowledge file needs updating. This can come from:\n- The user specifying a file directly\n- A feature that was just implemented or modified\n- A bug fix that revealed a non-obvious behavior\n\n### Step 3b: Read Current State\n\nRead the existing knowledge file and the relevant source code. Identify which sections are stale or incomplete.\n\n### Step 4b: Rewrite Affected Sections\n\nUpdate only the sections that need changes. Knowledge files describe the **present state** — rewrite sections entirely rather than appending notes or changelogs. Keep the same structure (Design Decisions, API Surface, Key Learnings \u002F Gotchas).\n\n### Step 5b: Write and Confirm\n\nWrite the updated file. Tell the user what was changed and why.\n\n---\n\n## Reviewing All Knowledge Files\n\n### Step 2c: Scan for Staleness\n\nFor each file in `knowledge\u002F`:\n1. Read the knowledge file\n2. Check if the source code it describes has changed significantly since the file was last written\n3. Flag files that appear outdated\n\n### Step 3c: Report\n\nPresent a summary listing each knowledge file with its status:\n- **Current** — the file accurately reflects the source code\n- **Needs update** — the source code has diverged; explain what looks stale\n- **Missing** — a significant feature area has source code but no knowledge file\n\nUse **AskQuestion** with `allow_multiple: true` to let the user pick which files to update, then follow the update flow above for each.\n","# Knowledge Management\n\nThis skill guides you through creating or updating files in the `knowledge\u002F` directory. Follow the conventions defined in `.cursor\u002Frules\u002Fknowledge.mdc`.\n\n## Step 1: Determine the Action\n\nUse AskQuestion:\n\n```\nprompt: \"What would you like to do?\"\noptions:\n  - Create a new knowledge file for a feature area\n  - Update an existing knowledge file\n  - Review all knowledge files for staleness\n```\n\n---\n\n## Creating a New Knowledge File\n\n### Step 2a: Identify the Feature Area\n\nAsk the user which feature area to document, or infer it from the conversation context. The file should be named after the feature area in lowercase with underscores (e.g., `knowledge\u002Fbilling.md`, `knowledge\u002Fauth.md`).\n\n### Step 3a: Explore the Codebase\n\nRead the source code for the feature area thoroughly:\n1. Identify the key modules, classes, and functions\n2. Trace the main code paths and data flow\n3. Note design decisions that are not obvious from the code alone\n4. Look for edge cases, gotchas, and non-obvious behaviors\n\nAlso read `knowledge\u002Farchitecture.md` to understand how this area fits into the overall system.\n\n### Step 4a: Draft the Knowledge File\n\nWrite the file following this structure:\n\n```markdown\n# \u003CFeature Area Name>\n\n\u003COne or two sentences describing what this area does.>\n\n## Design Decisions\n\n\u003CWhy it works the way it does. Trade-offs, constraints, alternatives considered. Use a heading per decision if there are several.>\n\n## API Surface\n\n\u003CKey classes, functions, types, and their relationships. Focus on what another developer (or the AI) needs to know to work in this area correctly.>\n\n## Key Learnings \u002F Gotchas\n\n\u003CNon-obvious behaviors, edge cases, things that broke before, common mistakes to avoid.>\n```\n\n### Step 5a: Write and Confirm\n\nWrite the file to `knowledge\u002F\u003Cfeature-area>.md`. Tell the user what was created and suggest they review it.\n\n---\n\n## Updating an Existing Knowledge File\n\n### Step 2b: Identify What Changed\n\nDetermine which knowledge file needs updating. This can come from:\n- The user specifying a file directly\n- A feature that was just implemented or modified\n- A bug fix that revealed a non-obvious behavior\n\n### Step 3b: Read Current State\n\nRead the existing knowledge file and the relevant source code. Identify which sections are stale or incomplete.\n\n### Step 4b: Rewrite Affected Sections\n\nUpdate only the sections that need changes. Knowledge files describe the **present state** — rewrite sections entirely rather than appending notes or changelogs. Keep the same structure (Design Decisions, API Surface, Key Learnings \u002F Gotchas).\n\n### Step 5b: Write and Confirm\n\nWrite the updated file. Tell the user what was changed and why.\n\n---\n\n## Reviewing All Knowledge Files\n\n### Step 2c: Scan for Staleness\n\nFor each file in `knowledge\u002F`:\n1. Read the knowledge file\n2. Check if the source code it describes has changed significantly since the file was last written\n3. Flag files that appear outdated\n\n### Step 3c: Report\n\nPresent a summary listing each knowledge file with its status:\n- **Current** — the file accurately reflects the source code\n- **Needs update** — the source code has diverged; explain what looks stale\n- **Missing** — a significant feature area has source code but no knowledge file\n\nUse **AskQuestion** with `allow_multiple: true` to let the user pick which files to update, then follow the update flow above for each.\n",{"name":5,"description":7},"main","ea5172c58cf8fe53f20b59482e62cc45741da12d",".cursor\u002Fskills\u002Fknowledge-management","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal","https:\u002F\u002Fgithub.com\u002Fcartaorobbin","2026-10-24 04:09:32",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add cartaorobbin\u002Fpyramid-temporal --skill knowledge-management",{"tool":50,"command":51},"bunx","bunx skills add cartaorobbin\u002Fpyramid-temporal --skill knowledge-management",{"tool":53,"command":54},"pnpm","pnpm dlx skills add cartaorobbin\u002Fpyramid-temporal --skill knowledge-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fknowledge-management\u002FSKILL.md",true,[],[59,79,98,121,132,146],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":69,"publishedAt":33},"01M6C1TXVJXMQ0VWWGMHD7PKG9","write-pytest","Write pytest tests for any Python codebase. Use when the user asks to write tests, create tests, add tests, or test a module\u002Fservice\u002Fendpoint\u002Ffunction. Framework-agnostic; routes to framework-specific helpers when signals are detected. Follows a research-then-discuss-then-write flow.","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwrite-pytest\u002FSKILL.md",[65,68],{"categoryNo":66,"categoryName":67,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[70,71,72,32,31,73,74,75,76,77,78,28],"write","write pytest","research","write tests","python","test","endpoint","flow","framework",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":88,"publishedAt":33},"01M6C1TTVR96XWX68FQY37S2QZ","quality-assurance","Run quality assurance checks on the current chat session — pre-task validation, post-task checklist, and code review. Use when finishing a task, before committing, or when the user asks for a QA review.","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fquality-assurance\u002FSKILL.md",[85],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",[89,90,91,92,93,94,95,96,31,97,32],"quality","quality assurance","run","code review","review","code","validation","qa","session",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":109,"publishedAt":33},"01M6C1TR2SWA481C00S2VQ12DW","python-developer","Python developer umbrella — installs Python coding conventions and bundles companion skills (best practices, testing, dependency management) in a single setup. Use when the user asks to set up Python development conventions, install Python skills, or says \"set up Python development\".","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fpython-developer\u002FSKILL.md",[104],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[110,74,111,112,113,25,31,114,115,32,116,117,118,119,120],"developer","python developer","SET","coding","dependency management","install","python development","best practices","testing","setup","development",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":33},"01M6C1TNAANT8RS9XKB2F3JF3E","python-best-practices","Comprehensive Python coding conventions and best practices. Use when the user asks about Python conventions, coding patterns, best practices, code style, anti-patterns, or \"how should I write this\" in Python.","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fpython-best-practices\u002FSKILL.md",[],[128,117,74,129,94,130,113,70,31,32,131],"python best practices","code style","how","anti-patterns",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":139,"publishedAt":33},"01M6C1TJEMGMNGNVE4DKWF4TNA","pyramid-library","Library Developer persona: developing standalone Pyramid extensions (own repo, own package) that expose includeme for external consumers. Use when the user builds a reusable Pyramid library, designs includeme for consumers, registers custom directives\u002Ftweens\u002Frequest methods, or tests a library with a proper app.","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fpyramid-library\u002FSKILL.md",[138],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},[140,141,142,143,144,110,145,31,32],"pyramid library","library","repo","core","package","persona",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":153,"publishedAt":33},"01M6C1TFT8Z6MCBEAQ7S24XQ77","pyramid-developer","Pyramid framework conventions — configuration\u002Fregistry, module system with includeme, pyramid_services, models, Cornice REST, ACL authorization, and transactions. Use when setting up Pyramid development conventions for a project.","https:\u002F\u002Fgithub.com\u002Fcartaorobbin\u002Fpyramid-temporal\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fpyramid-developer\u002FSKILL.md",[152],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},[154,110,120,155,78,156,157,158,159,160,161,32,162,74],"pyramid developer","registry","services","ACL","REST","authorization","transactions","system","micromonolith"]