[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EXH3AJ29G0KBAC0H2NK9DM":3,"skill-same:01M7EXH3AJ29G0KBAC0H2NK9DM":64},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7EXH3AJ29G0KBAC0H2NK9DM","build-cs-skill",null,"CodeStable skill authoring and evolution protocol. Use when creating, refactoring, simplifying, or reviewing cs-* skills under plugins\u002Fcodestable\u002Fskills or .claude\u002Fskills. Produces a thin harness, an explicit context plan, evidence gates, and an optional agent collaboration contract. Do not use for product implementation; use eval-cs-skill only for measured experiment loops.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbuild-cs-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: build-cs-skill\ndescription: \"CodeStable skill authoring and evolution protocol. Use when creating, refactoring, simplifying, or reviewing cs-* skills under plugins\u002Fcodestable\u002Fskills or .claude\u002Fskills. Produces a thin harness, an explicit context plan, evidence gates, and an optional agent collaboration contract. Do not use for product implementation; use eval-cs-skill only for measured experiment loops.\"\n---\n\n# build-cs-skill\n\n## Purpose\n\nBuild the smallest always-loaded control surface that lets an agent select relevant context, respect\nhard gates, collaborate safely, and leave recoverable evidence. `SKILL.md` is the **thin harness**;\nreferences and repository facts are **thick context**. Thick means decision-useful, not large.\n\nSpecify responsibility, authority, context selection, evidence, and stop conditions. Leave safe\nimplementation choices to the executing agent.\n\n## Scope And References\n\nTargets are `plugins\u002Fcodestable\u002Fskills\u002F\u003Cskill-name>\u002F` or `.claude\u002Fskills\u002F\u003Clocal-skill-name>\u002F`.\n\nLoad only the reference needed for the current decision:\n\n- `references\u002Fcs-skill-spec-standard.md`: contract definitions, typed decisions, recovery, and output semantics.\n- `references\u002Fcs-skill-quality-gates.md`: review algorithm for placement, context, evolution, runtime alignment, and validation safety.\n- `references\u002Fcs-skill-fixture-patterns.md`: risky routing, checkpoint, failure, compatibility, or\n  forbidden-action scenarios.\n\n## Spec\n\n```haskell\ndata SkillKind\n  = OperatorSkill | WorkflowSkill | MethodologySkill | CompatibilityShim | ReferenceDoc\n\ndata SkillShape = NoActiveSkill | ThinOperator | ContextualWorkflow | ToolBackedWorkflow\n                | ShimSkill | ReferenceSkill\ndata ProcessProtocol = WorkflowProtocol | DomainProtocol | LifecycleProtocol\n                     | OperationProtocol | AlgorithmProtocol | ShimRoute | ReferenceOnly\ndata RulePlacement = Harness | StageContext | ProjectContext | DeterministicGate | Remove\ndata DelegationRole = Orchestrator | LeafExecutor\n\nselectSkillShape :: SkillKind -> SkillSource -> SkillShape\nselectSkillShape kind source | not (independentSkillNeeded kind source) = NoActiveSkill\nselectSkillShape kind source =\n  case kind of\n    ReferenceDoc      -> ReferenceSkill\n    CompatibilityShim -> ShimSkill\n    OperatorSkill     -> ThinOperator\n    WorkflowSkill\n      | deterministicRouter source -> ToolBackedWorkflow\n      | otherwise                  -> ContextualWorkflow\n    MethodologySkill  -> ContextualWorkflow\n\nselectProcessProtocol :: SkillKind -> SkillSource -> ProcessProtocol\nselectProcessProtocol kind source =\n  case kind of\n    WorkflowSkill\n      | lifecycleDriven source -> LifecycleProtocol\n      | otherwise              -> WorkflowProtocol\n    OperatorSkill\n      | algorithmic source -> AlgorithmProtocol\n      | otherwise          -> OperationProtocol\n    MethodologySkill  -> DomainProtocol\n    CompatibilityShim -> ShimRoute\n    ReferenceDoc      -> ReferenceOnly\n\nplaceRule :: Rule -> RulePlacement\nplaceRule r\n  | mechanizable r                                    = DeterministicGate\n  | nonMechanizableSafety r                           = Harness\n  | projectSpecific r                                 = ProjectContext\n  | stageSpecific r                                   = StageContext\n  | everyInvocationNeeds r && changesDecisionOrGate r = Harness\n  | otherwise                                         = Remove\n\nbuildContextPlan :: SkillShape -> [PlacedRule] -> ContextPlan\nbuildThinHarness :: SkillShape -> ResponsibilityContract -> ContextPlan -> Markdown\n```\n\n## Build Protocol\n\n### 1. Establish scope and responsibility\n\nRead the target and relevant repository design facts; inspect git status and preserve unrelated edits.\nState the one outcome the skill owns, its authority boundary, completion evidence, and unsafe stop\nconditions. Authoring itself does not require project preflight. A generated skill adds preflight only\nwhen its behavior depends on project setup, repository facts, artifact writes, or recovery.\n\nIf there is no independent installable responsibility, or an existing skill\u002Freference\u002Ftool owns it,\nselect `NoActiveSkill`. A retired v1 CodeStable name also selects `NoActiveSkill`; migration prose is\nnot an instruction to recreate a compatibility shim. Use `ReferenceSkill` only when knowledge has an\nindependent distribution contract.\n\n### 2. Choose the minimum shape\n\nClassify before writing; do not default to a full protocol refactor. Use `ThinOperator` for one\naction\u002Fartifact, `ContextualWorkflow` for staged or recoverable work, and `ToolBackedWorkflow` when a\ndeterministic router\u002Fgate owns fragile choices. `ShimSkill` contains only a canonical target and\npreset, and is allowed only when a newly accepted distribution contract explicitly ships that alias.\n`ReferenceSkill` contains knowledge without an invented workflow.\n\nUse high freedom for safe implementation choices, medium for preferred patterns, and low only for\nfragile operations or invariant-sensitive ordering.\n\n### 3. Place every rule once\n\nInventory current and proposed rules before editing. Record each rule's source, affected decision,\nfrequency, and `RulePlacement`; then apply `placeRule`.\n\n- Mechanizable safety and repeated transformations -> script, hook, or gate.\n- Stage methods, templates, and examples -> stage reference.\n- Project facts, ADRs, and learnings -> repository CodeStable artifacts.\n- Every-invocation decisions and non-mechanizable hard gates -> harness.\n- Generic advice, duplicated rationale, stale prose, and behavior-neutral steps -> remove.\n\nInformation must have one canonical home. Do not retain the same route, gate, or method in both the\nharness and a prose reference.\n\n### 4. Build the context plan before the harness\n\nCall `buildContextPlan` before writing the body. For every context source state when to load it, why\nit matters, how freshness is checked, when enough context has been gathered, and how an already\nloaded fact is reused.\n\nEntry context is the minimum needed for a safe next action. After selection, load one stage protocol\nand only relevant facts\u002Fsupport. Do not preload every reference, ADR, note, or source file.\n\n### 5. Write the thin harness\n\nWrite the runtime kernel in this order: trigger\u002Ffrontmatter, responsibility, context contract,\ndecision contract when needed, hard gates, collaboration when needed, and done\u002Ffailure.\n\nTarget review thresholds: 30-80 body lines for an operator, 60-120 for a workflow front door, and at\nmost 40 for a shim. Exceeding them requires another placement pass and an explicit reason, not truncation.\n\nDo not include long rationale, historical narrative, broad checklists, templates, or ordinary coding\nsteps in the harness. Preserve a compact `## Operation`, `## Workflow`, or `## Lifecycle` only when\nit helps a fresh agent orient from entry to recoverable exit.\n\n### 6. Add collaboration only when useful\n\nDelegate only bounded work that has explicit ownership and an independent completion check. Do not\npre-script provider-specific roles or a fixed agent count.\n\nKeep shipped harnesses backend-agnostic: describe capabilities, never product names; exact backend\u002Fmodel pins belong to `ProjectContext`.\nBefore creating a reviewer, discover subagent creation and management capabilities callable in the current session. Do not substitute a `PATH` executable scan for capability discovery.\nReviewer creation methods prefer managed structured delegation with fresh context, explicit model selection, workspace access, lifecycle control, and a terminal report; then a host subagent; use a bounded one-shot agent CLI only as fallback. Explicitly select the strongest stable qualified model, preferring heterogeneity only after the quality floor is met.\n\nA healthy running delegation stays bound to its run and target; a queryable active `Awaiting` run remains healthy, and a better creation method found later does not justify cancellation or duplicate dispatch.\nSwitch only after terminal failure without a report, loss of recoverable run identity, a capability mismatch, or target invalidation.\n\nClassify topology before dispatch. A delegated agent defaults to `LeafExecutor` unless its explicit\nresponsibility is orchestration. A `LeafExecutor` must not dispatch another agent, wake or follow up\na child, or invoke itself or an alias. Only an `Orchestrator` owns further delegation.\n\nUse this packet contract:\n\n```text\ncontextPacket = goal + relevantContext + scopeOwnership + boundaries + evidence + returnContract\nmainAgentOwnsIntegration = true\n```\n\nThe delegated agent chooses its route. The calling orchestrator owns integration, conflict handling,\nfinal verification, and durable state. It waits for the return contract; treat idle without a return\npayload and no recoverable run identity as failed delegation, not permission to resend the task blindly.\nWorktree\u002Fbranch policy remains host-owned.\n\n### 7. Preserve hard contracts\n\n#### Haskell Contract Gate\n\nUse Haskell only for a real closed decision, transition, lifecycle, or invariant. Prompt-routed\nworkflows keep one compact decision truth and no parallel prose router. Audit every stage checkpoint\nagainst the canonical main entry's tagged resume domain; persist `Awaiting` state, reason, and run\nidentity. A locally closed stage type is insufficient.\n\n#### Runtime Alignment Gate\n\nFor `ToolBackedWorkflow`, state the tool contract, invariant boundaries, outcomes, and failure\nbehavior without copying its branch table. Align persisted schema, normalization, terminal\nprecedence, and outcomes across harness, runtime, references, and tests.\n\nEach skill remains independently installable: do not require sibling skill files or a centralized\nonboard runtime. Skill-specific context and deterministic helpers belong to the owning skill's\n`references\u002F` and `scripts\u002F`. Project context belongs in `.codestable\u002Fattention.md`,\n`.codestable\u002Flessons\u002F`, `.codestable\u002Fwork\u002F`, or the project's existing docs and ADRs. A v2 skill may\nsearch useful v1 artifacts, but must not execute their tools or treat them as current distribution\nsurfaces. Shims stay thin. Branch\u002Fworktree policy and agent backends remain host-owned.\n\n### 8. Compress, validate, and finish\n\nFor continuous evolution, feed every new lesson back through `placeRule`; never treat it as permission\nto append prose. Replace obsolete rules, move specialized knowledge to context, and run a whole-file\ndeletion pass. Additive-only evolution is a failure mode.\n\nUpdate related skills, shared references, tests, and ADR wording when the changed contract crosses\nthose boundaries. Do not add changelog or migration narrative to the runtime skill.\n\nLoad `references\u002Fcs-skill-quality-gates.md` and create a validation plan. Apply its `Regression Ladder`,\n`Live Host Safety Gate`, and family coverage as applicable. Structural contracts do not replace\nscenario or real runtime conformance tests.\n\nRun relevant repository tests and `git diff --check`. Use `eval-cs-skill` only when the request\nexplicitly includes a measured multi-model experiment or when release policy requires one.\n\n## Failure Behavior\n\nReturn `NeedsHuman` when the target\u002Foutput is ambiguous, overlapping edits cannot be preserved,\nauthority boundaries conflict, required context cannot be identified, or the proposed compression\nwould remove a recovery\u002Fsafety contract. Report the current target, blocker, preserved files, and\nsafe next action.\n\n## Output Contract\n\nReport:\n\n- target skill path and `SkillShape`;\n- one-sentence responsibility and selected freedom;\n- rule placements: kept in harness, moved to stage\u002Fproject context, mechanized, or removed;\n- context plan and collaboration contract, or why none is needed;\n- files changed;\n- validation results and skipped layers;\n- unresolved maintainer decisions and the next concrete action.\n\nDistinguish actual edits from recommendations. Do not claim success from line reduction alone; the\nresult must remain safe, recoverable, and usable by a fresh agent without chat history.\n","# build-cs-skill\n\n## Purpose\n\nBuild the smallest always-loaded control surface that lets an agent select relevant context, respect\nhard gates, collaborate safely, and leave recoverable evidence. `SKILL.md` is the **thin harness**;\nreferences and repository facts are **thick context**. Thick means decision-useful, not large.\n\nSpecify responsibility, authority, context selection, evidence, and stop conditions. Leave safe\nimplementation choices to the executing agent.\n\n## Scope And References\n\nTargets are `plugins\u002Fcodestable\u002Fskills\u002F\u003Cskill-name>\u002F` or `.claude\u002Fskills\u002F\u003Clocal-skill-name>\u002F`.\n\nLoad only the reference needed for the current decision:\n\n- `references\u002Fcs-skill-spec-standard.md`: contract definitions, typed decisions, recovery, and output semantics.\n- `references\u002Fcs-skill-quality-gates.md`: review algorithm for placement, context, evolution, runtime alignment, and validation safety.\n- `references\u002Fcs-skill-fixture-patterns.md`: risky routing, checkpoint, failure, compatibility, or\n  forbidden-action scenarios.\n\n## Spec\n\n```haskell\ndata SkillKind\n  = OperatorSkill | WorkflowSkill | MethodologySkill | CompatibilityShim | ReferenceDoc\n\ndata SkillShape = NoActiveSkill | ThinOperator | ContextualWorkflow | ToolBackedWorkflow\n                | ShimSkill | ReferenceSkill\ndata ProcessProtocol = WorkflowProtocol | DomainProtocol | LifecycleProtocol\n                     | OperationProtocol | AlgorithmProtocol | ShimRoute | ReferenceOnly\ndata RulePlacement = Harness | StageContext | ProjectContext | DeterministicGate | Remove\ndata DelegationRole = Orchestrator | LeafExecutor\n\nselectSkillShape :: SkillKind -> SkillSource -> SkillShape\nselectSkillShape kind source | not (independentSkillNeeded kind source) = NoActiveSkill\nselectSkillShape kind source =\n  case kind of\n    ReferenceDoc      -> ReferenceSkill\n    CompatibilityShim -> ShimSkill\n    OperatorSkill     -> ThinOperator\n    WorkflowSkill\n      | deterministicRouter source -> ToolBackedWorkflow\n      | otherwise                  -> ContextualWorkflow\n    MethodologySkill  -> ContextualWorkflow\n\nselectProcessProtocol :: SkillKind -> SkillSource -> ProcessProtocol\nselectProcessProtocol kind source =\n  case kind of\n    WorkflowSkill\n      | lifecycleDriven source -> LifecycleProtocol\n      | otherwise              -> WorkflowProtocol\n    OperatorSkill\n      | algorithmic source -> AlgorithmProtocol\n      | otherwise          -> OperationProtocol\n    MethodologySkill  -> DomainProtocol\n    CompatibilityShim -> ShimRoute\n    ReferenceDoc      -> ReferenceOnly\n\nplaceRule :: Rule -> RulePlacement\nplaceRule r\n  | mechanizable r                                    = DeterministicGate\n  | nonMechanizableSafety r                           = Harness\n  | projectSpecific r                                 = ProjectContext\n  | stageSpecific r                                   = StageContext\n  | everyInvocationNeeds r && changesDecisionOrGate r = Harness\n  | otherwise                                         = Remove\n\nbuildContextPlan :: SkillShape -> [PlacedRule] -> ContextPlan\nbuildThinHarness :: SkillShape -> ResponsibilityContract -> ContextPlan -> Markdown\n```\n\n## Build Protocol\n\n### 1. Establish scope and responsibility\n\nRead the target and relevant repository design facts; inspect git status and preserve unrelated edits.\nState the one outcome the skill owns, its authority boundary, completion evidence, and unsafe stop\nconditions. Authoring itself does not require project preflight. A generated skill adds preflight only\nwhen its behavior depends on project setup, repository facts, artifact writes, or recovery.\n\nIf there is no independent installable responsibility, or an existing skill\u002Freference\u002Ftool owns it,\nselect `NoActiveSkill`. A retired v1 CodeStable name also selects `NoActiveSkill`; migration prose is\nnot an instruction to recreate a compatibility shim. Use `ReferenceSkill` only when knowledge has an\nindependent distribution contract.\n\n### 2. Choose the minimum shape\n\nClassify before writing; do not default to a full protocol refactor. Use `ThinOperator` for one\naction\u002Fartifact, `ContextualWorkflow` for staged or recoverable work, and `ToolBackedWorkflow` when a\ndeterministic router\u002Fgate owns fragile choices. `ShimSkill` contains only a canonical target and\npreset, and is allowed only when a newly accepted distribution contract explicitly ships that alias.\n`ReferenceSkill` contains knowledge without an invented workflow.\n\nUse high freedom for safe implementation choices, medium for preferred patterns, and low only for\nfragile operations or invariant-sensitive ordering.\n\n### 3. Place every rule once\n\nInventory current and proposed rules before editing. Record each rule's source, affected decision,\nfrequency, and `RulePlacement`; then apply `placeRule`.\n\n- Mechanizable safety and repeated transformations -> script, hook, or gate.\n- Stage methods, templates, and examples -> stage reference.\n- Project facts, ADRs, and learnings -> repository CodeStable artifacts.\n- Every-invocation decisions and non-mechanizable hard gates -> harness.\n- Generic advice, duplicated rationale, stale prose, and behavior-neutral steps -> remove.\n\nInformation must have one canonical home. Do not retain the same route, gate, or method in both the\nharness and a prose reference.\n\n### 4. Build the context plan before the harness\n\nCall `buildContextPlan` before writing the body. For every context source state when to load it, why\nit matters, how freshness is checked, when enough context has been gathered, and how an already\nloaded fact is reused.\n\nEntry context is the minimum needed for a safe next action. After selection, load one stage protocol\nand only relevant facts\u002Fsupport. Do not preload every reference, ADR, note, or source file.\n\n### 5. Write the thin harness\n\nWrite the runtime kernel in this order: trigger\u002Ffrontmatter, responsibility, context contract,\ndecision contract when needed, hard gates, collaboration when needed, and done\u002Ffailure.\n\nTarget review thresholds: 30-80 body lines for an operator, 60-120 for a workflow front door, and at\nmost 40 for a shim. Exceeding them requires another placement pass and an explicit reason, not truncation.\n\nDo not include long rationale, historical narrative, broad checklists, templates, or ordinary coding\nsteps in the harness. Preserve a compact `## Operation`, `## Workflow`, or `## Lifecycle` only when\nit helps a fresh agent orient from entry to recoverable exit.\n\n### 6. Add collaboration only when useful\n\nDelegate only bounded work that has explicit ownership and an independent completion check. Do not\npre-script provider-specific roles or a fixed agent count.\n\nKeep shipped harnesses backend-agnostic: describe capabilities, never product names; exact backend\u002Fmodel pins belong to `ProjectContext`.\nBefore creating a reviewer, discover subagent creation and management capabilities callable in the current session. Do not substitute a `PATH` executable scan for capability discovery.\nReviewer creation methods prefer managed structured delegation with fresh context, explicit model selection, workspace access, lifecycle control, and a terminal report; then a host subagent; use a bounded one-shot agent CLI only as fallback. Explicitly select the strongest stable qualified model, preferring heterogeneity only after the quality floor is met.\n\nA healthy running delegation stays bound to its run and target; a queryable active `Awaiting` run remains healthy, and a better creation method found later does not justify cancellation or duplicate dispatch.\nSwitch only after terminal failure without a report, loss of recoverable run identity, a capability mismatch, or target invalidation.\n\nClassify topology before dispatch. A delegated agent defaults to `LeafExecutor` unless its explicit\nresponsibility is orchestration. A `LeafExecutor` must not dispatch another agent, wake or follow up\na child, or invoke itself or an alias. Only an `Orchestrator` owns further delegation.\n\nUse this packet contract:\n\n```text\ncontextPacket = goal + relevantContext + scopeOwnership + boundaries + evidence + returnContract\nmainAgentOwnsIntegration = true\n```\n\nThe delegated agent chooses its route. The calling orchestrator owns integration, conflict handling,\nfinal verification, and durable state. It waits for the return contract; treat idle without a return\npayload and no recoverable run identity as failed delegation, not permission to resend the task blindly.\nWorktree\u002Fbranch policy remains host-owned.\n\n### 7. Preserve hard contracts\n\n#### Haskell Contract Gate\n\nUse Haskell only for a real closed decision, transition, lifecycle, or invariant. Prompt-routed\nworkflows keep one compact decision truth and no parallel prose router. Audit every stage checkpoint\nagainst the canonical main entry's tagged resume domain; persist `Awaiting` state, reason, and run\nidentity. A locally closed stage type is insufficient.\n\n#### Runtime Alignment Gate\n\nFor `ToolBackedWorkflow`, state the tool contract, invariant boundaries, outcomes, and failure\nbehavior without copying its branch table. Align persisted schema, normalization, terminal\nprecedence, and outcomes across harness, runtime, references, and tests.\n\nEach skill remains independently installable: do not require sibling skill files or a centralized\nonboard runtime. Skill-specific context and deterministic helpers belong to the owning skill's\n`references\u002F` and `scripts\u002F`. Project context belongs in `.codestable\u002Fattention.md`,\n`.codestable\u002Flessons\u002F`, `.codestable\u002Fwork\u002F`, or the project's existing docs and ADRs. A v2 skill may\nsearch useful v1 artifacts, but must not execute their tools or treat them as current distribution\nsurfaces. Shims stay thin. Branch\u002Fworktree policy and agent backends remain host-owned.\n\n### 8. Compress, validate, and finish\n\nFor continuous evolution, feed every new lesson back through `placeRule`; never treat it as permission\nto append prose. Replace obsolete rules, move specialized knowledge to context, and run a whole-file\ndeletion pass. Additive-only evolution is a failure mode.\n\nUpdate related skills, shared references, tests, and ADR wording when the changed contract crosses\nthose boundaries. Do not add changelog or migration narrative to the runtime skill.\n\nLoad `references\u002Fcs-skill-quality-gates.md` and create a validation plan. Apply its `Regression Ladder`,\n`Live Host Safety Gate`, and family coverage as applicable. Structural contracts do not replace\nscenario or real runtime conformance tests.\n\nRun relevant repository tests and `git diff --check`. Use `eval-cs-skill` only when the request\nexplicitly includes a measured multi-model experiment or when release policy requires one.\n\n## Failure Behavior\n\nReturn `NeedsHuman` when the target\u002Foutput is ambiguous, overlapping edits cannot be preserved,\nauthority boundaries conflict, required context cannot be identified, or the proposed compression\nwould remove a recovery\u002Fsafety contract. Report the current target, blocker, preserved files, and\nsafe next action.\n\n## Output Contract\n\nReport:\n\n- target skill path and `SkillShape`;\n- one-sentence responsibility and selected freedom;\n- rule placements: kept in harness, moved to stage\u002Fproject context, mechanized, or removed;\n- context plan and collaboration contract, or why none is needed;\n- files changed;\n- validation results and skipped layers;\n- unresolved maintainer decisions and the next concrete action.\n\nDistinguish actual edits from recommendations. Do not claim success from line reduction alone; the\nresult must remain safe, recoverable, and usable by a fresh agent without chat history.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fbuild-cs-skill",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill build-cs-skill",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill build-cs-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill build-cs-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbuild-cs-skill\u002FSKILL.md",true,[46,52,56,60],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",301,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbuild-cs-skill\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcs-skill-fixture-patterns.md",9249,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbuild-cs-skill\u002Freferences\u002Fcs-skill-fixture-patterns.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fcs-skill-quality-gates.md",15655,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbuild-cs-skill\u002Freferences\u002Fcs-skill-quality-gates.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fcs-skill-spec-standard.md",15113,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbuild-cs-skill\u002Freferences\u002Fcs-skill-spec-standard.md",[65,73,78,85,92,99],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":72},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":74,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":72},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":72},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":72},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":72},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":72},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]