[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75P2542FWBMYF40V0N3EPF5":3,"skill-same:01M75P2542FWBMYF40V0N3EPF5":51},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M75P2542FWBMYF40V0N3EPF5","seam-detection",null,"Use when scanning a diff for protected changes or reviewing widened permissions, secrets, storage, or runtime contracts. Detects registered seam crossings and agent-runtime exit-code changes, and defines the finding format.","pixeloven\u002Fcrew","pixeloven","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5751260?v=4","01M75P0048G371B0AWRKQ7FJN8","PixelOven","01M75P0051RK1ZEY0SA9HCMX2Z",1,"MIT","https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Fskills\u002Fseam-detection\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: seam-detection\ndescription: Use when scanning a diff for protected changes or reviewing widened permissions, secrets, storage, or runtime contracts. Detects registered seam crossings and agent-runtime exit-code changes, and defines the finding format.\ntier: concept\nrequires: []\nexpects-local: [protected-seams, secret-paths]\n---\n\nA seam crossing is any change that touches a protected pattern in the project's seams registry without the crossing having been explicitly flagged by the author. The registry is a **consumer-local** skill; the shapes below are common ones, and a consumer's registry may add or drop entries. This skill defines how to detect crossings in practice.\n\n## Detecting by registry\n\nRead the project's `protected-seams` registry first. Each entry names the protected pattern, the files it lives in, and how to grep for it. For each entry:\n\n1. Run its grep against the changed files (`git diff \u003Cbase>...HEAD -- \u003Cpaths>`), not the whole tree.\n2. Read every hit in context and decide whether the change alters the protected contract or only touches the file (see False positives).\n3. Report each crossing in the finding format below.\n\nA stack pack may seed registry entries for its own shapes (Kubernetes secret sync, scheduling, RBAC, an LLM or tool gateway's access lists); the registry entry, not the pack, is what you scan for. Whatever the registry says, always scan for hardcoded secrets — any string matching key, token, password or API-key patterns — with the project's secret scanner (`gitleaks detect --source . --no-git` is one example) and the `secret-paths` local skill.\n\n## Common shapes\n\nMost registries hold some of these. Each is described by what it protects, not by product:\n\n- **Secret contract** — how secrets reach workloads: which store they come from, how often they refresh, what happens to them on delete, and that each synced secret has a consumer.\n- **Scheduling contract** — where workloads may run and on what storage: placement rules, storage tiers, and static-volume bindings.\n- **Access boundary** — which callers may reach which tools or services through a gateway: allowlists, access groups, and what an empty list means. An empty list that fails *open* is the crossing to look for first.\n- **Runtime contract** — the agent runtime's exit codes, result schema and retry policy (below).\n- **Authorization widening** — a grant that lets an identity do more than before: new bindings, new verbs on existing rules, wildcards, escalation-adjacent permissions, broad subjects, or a wider scope where a narrow one would do.\n\nFor authorization widening, report the *delta in authority*, not just the diff: what could this identity do after the change that it couldn't before, and what is the worst thing that new permission allows on the named resources? A report-only auditor that gains a delete permission becomes an armed reaper **with no code change**.\n\n### Seam 4 — Agent runtime contract\n\nOnly applies where a project runs its own autonomous runtime. The **concrete** contract — which exit codes mean what, the result schema and its path, the retry expression — belongs to that project's agent-runtime local skill; this is the shape to watch for.\n\n**Scan for in diffs:**\n- Exit-code semantics changed anywhere the runtime's success\u002Ftransient\u002Fstructural distinction is encoded (orchestrator, workflow template, wrapper script)\n- The structured result schema — fields added, renamed, or removed — or the path it's written to\n- Retry policy decoupled from the exit-code contract (e.g. a retry expression edited, or a duration cap re-introduced)\n- Runner image version bumped without a corresponding compatibility check against the orchestrator it hosts\n\n**Shell grep** (adjust the paths to the project's runtime):\n```bash\ngit diff HEAD~1 -- '*orchestrator*' '*[Ww]orkflow*' | grep -E '(exit|retry|[Rr]esult|maxDuration)'\n```\n\n## Reporting a seam finding\n\nIn a PR comment or review finding:\n\n```\n**Seam crossing detected — \u003Cseam name>**\n\nFile: \u003Cpath>\nLine: \u003Cnumber>\nChange: \u003Cwhat changed>\nRisk: \u003Cwhy this matters>\nAction required: Human sign-off before merge. Tag @\u003Cproject-approver>.\n```\n\nMark as **Required** in the review. Do not approve or suggest merge until the author acknowledges the crossing and the project approver provides sign-off.\n\n## False positives\n\nNot every touch of a seam-related file is a crossing. Context matters:\n\n- A secret-sync manifest modified to add a label, without touching its store, refresh or delete behaviour, is not a crossing\n- A comment or logging change in a runtime orchestrator is not a crossing\n- A new test that imports the runtime's result type but doesn't change its schema is not a crossing\n- A new grant that only adds read access to resources the identity could already read is worth a Note, not a Required finding\n\nWhen in doubt, flag it. A false positive costs a brief discussion. A missed crossing can break production.\n","A seam crossing is any change that touches a protected pattern in the project's seams registry without the crossing having been explicitly flagged by the author. The registry is a **consumer-local** skill; the shapes below are common ones, and a consumer's registry may add or drop entries. This skill defines how to detect crossings in practice.\n\n## Detecting by registry\n\nRead the project's `protected-seams` registry first. Each entry names the protected pattern, the files it lives in, and how to grep for it. For each entry:\n\n1. Run its grep against the changed files (`git diff \u003Cbase>...HEAD -- \u003Cpaths>`), not the whole tree.\n2. Read every hit in context and decide whether the change alters the protected contract or only touches the file (see False positives).\n3. Report each crossing in the finding format below.\n\nA stack pack may seed registry entries for its own shapes (Kubernetes secret sync, scheduling, RBAC, an LLM or tool gateway's access lists); the registry entry, not the pack, is what you scan for. Whatever the registry says, always scan for hardcoded secrets — any string matching key, token, password or API-key patterns — with the project's secret scanner (`gitleaks detect --source . --no-git` is one example) and the `secret-paths` local skill.\n\n## Common shapes\n\nMost registries hold some of these. Each is described by what it protects, not by product:\n\n- **Secret contract** — how secrets reach workloads: which store they come from, how often they refresh, what happens to them on delete, and that each synced secret has a consumer.\n- **Scheduling contract** — where workloads may run and on what storage: placement rules, storage tiers, and static-volume bindings.\n- **Access boundary** — which callers may reach which tools or services through a gateway: allowlists, access groups, and what an empty list means. An empty list that fails *open* is the crossing to look for first.\n- **Runtime contract** — the agent runtime's exit codes, result schema and retry policy (below).\n- **Authorization widening** — a grant that lets an identity do more than before: new bindings, new verbs on existing rules, wildcards, escalation-adjacent permissions, broad subjects, or a wider scope where a narrow one would do.\n\nFor authorization widening, report the *delta in authority*, not just the diff: what could this identity do after the change that it couldn't before, and what is the worst thing that new permission allows on the named resources? A report-only auditor that gains a delete permission becomes an armed reaper **with no code change**.\n\n### Seam 4 — Agent runtime contract\n\nOnly applies where a project runs its own autonomous runtime. The **concrete** contract — which exit codes mean what, the result schema and its path, the retry expression — belongs to that project's agent-runtime local skill; this is the shape to watch for.\n\n**Scan for in diffs:**\n- Exit-code semantics changed anywhere the runtime's success\u002Ftransient\u002Fstructural distinction is encoded (orchestrator, workflow template, wrapper script)\n- The structured result schema — fields added, renamed, or removed — or the path it's written to\n- Retry policy decoupled from the exit-code contract (e.g. a retry expression edited, or a duration cap re-introduced)\n- Runner image version bumped without a corresponding compatibility check against the orchestrator it hosts\n\n**Shell grep** (adjust the paths to the project's runtime):\n```bash\ngit diff HEAD~1 -- '*orchestrator*' '*[Ww]orkflow*' | grep -E '(exit|retry|[Rr]esult|maxDuration)'\n```\n\n## Reporting a seam finding\n\nIn a PR comment or review finding:\n\n```\n**Seam crossing detected — \u003Cseam name>**\n\nFile: \u003Cpath>\nLine: \u003Cnumber>\nChange: \u003Cwhat changed>\nRisk: \u003Cwhy this matters>\nAction required: Human sign-off before merge. Tag @\u003Cproject-approver>.\n```\n\nMark as **Required** in the review. Do not approve or suggest merge until the author acknowledges the crossing and the project approver provides sign-off.\n\n## False positives\n\nNot every touch of a seam-related file is a crossing. Context matters:\n\n- A secret-sync manifest modified to add a label, without touching its store, refresh or delete behaviour, is not a crossing\n- A comment or logging change in a runtime orchestrator is not a crossing\n- A new test that imports the runtime's result type but doesn't change its schema is not a crossing\n- A new grant that only adds read access to resources the identity could already read is worth a Note, not a Required finding\n\nWhen in doubt, flag it. A false positive costs a brief discussion. A missed crossing can break production.\n",{"name":5,"tier":24,"requires":25,"description":7,"expects-local":26},"concept",[],[27,28],"protected-seams","secret-paths","main","686d42537f9efddb1aeece969b1a4fee2e4d1a88","skills\u002Fseam-detection",0,"https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew","https:\u002F\u002Fgithub.com\u002Fpixeloven","www.pixeloven.com","2026-11-07 09:18:41",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add pixeloven\u002Fcrew --skill seam-detection",{"tool":43,"command":44},"bunx","bunx skills add pixeloven\u002Fcrew --skill seam-detection",{"tool":46,"command":47},"pnpm","pnpm dlx skills add pixeloven\u002Fcrew --skill seam-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Fskills\u002Fseam-detection\u002FSKILL.md",true,[],[52,59,66,73,79,85],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M75P2X72QCY4H2H6C7D3KQ1Z","orchard-gh-runs","Use when reading a failed GitHub Actions run with the gh CLI in this project, before re-running it or reporting a CI failure, so the failing step's log is read instead of the whole run.","https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fproposals\u002Forchard\u002F.agents\u002Fskills\u002Forchard-gh-runs\u002FSKILL.md",[],[],{"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":65,"publishedAt":19},"01M75P2T76B22B314Q3W25GDCK","orchard-gh","Hand-edited after promotion; the learned marker was dropped, so Doctor and check_skills --local can no longer see it.","https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fproposals\u002Finvalid\u002F.agents\u002Fskills\u002Forchard-gh\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M75P2Q410WX0H3ZZ61R210F4","demo-topology","Use when exercising the inventory contract fixture so that this fixture description comfortably clears the schema-v2 minimum length.","https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finventory\u002Fproject\u002F.agents\u002Fskills\u002Fdemo-topology\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M75P2KTWZ94KNSKHPGFB6Y6J","helper-jq","https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finventory\u002Fhome\u002F.codex\u002Fplugins\u002Fcache\u002Facme\u002Fhelper\u002F2.0.0\u002Fskills\u002Fhelper-jq\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":69,"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":19},"01M75P2GT2CXZR4EZE2DS9GTS7","user-notes","https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finventory\u002Fhome\u002F.claude\u002Fskills\u002Fuser-notes\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M75P2D61GDSH9NFNEBV4HDBS","toolkit-gh","https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finventory\u002Fhome\u002F.claude\u002Fplugins\u002Fcache\u002Facme\u002Ftoolkit\u002F1.2.0\u002Fskills\u002Ftoolkit-gh\u002FSKILL.md",[],[]]