[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WWP4678SE7NHW7F7D0WTG7":3,"skill-same:01M6WWP4678SE7NHW7F7D0WTG7":225},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":88,"commitSha":89,"skillDirectory":90,"forksCount":14,"repositoryHtmlUrl":91,"repositoryHomepageUrl":92,"ownerHtmlUrl":93,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":94,"install":95,"resources":107},"01M6WWP4678SE7NHW7F7D0WTG7","skill-gate",null,"Session-start meta-skill that enforces the 1% rule: before any action\non a processkit entity or context\u002F file, if there is even a 1% chance\na processkit skill applies, you MUST check skill-finder first. Load\nthis skill at the start of every session that may involve processkit\nwork. Use when beginning a new task, when unsure which skill applies,\nor when you are about to edit context\u002F, create an entity, or run an\nMCP tool.","projectious-work\u002Fprocesskit","projectious-work","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263889726?v=4","01M6N97TJJ118WQ35CHRV8RD0E","projectious.work","01M6N97TPWJPF0BMKYQ4PBY5W8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"skill gate","gate","meta-skill","when","project test","project build","at","which","you","new task","project","MCP","command","branch","work","Meta","run","create","notes","review","2026-11-10 10:12:30",false,"---\nname: skill-gate\ndescription: |\n  Session-start meta-skill that enforces the 1% rule: before any action\n  on a processkit entity or context\u002F file, if there is even a 1% chance\n  a processkit skill applies, you MUST check skill-finder first. Load\n  this skill at the start of every session that may involve processkit\n  work. Use when beginning a new task, when unsure which skill applies,\n  or when you are about to edit context\u002F, create an entity, or run an\n  MCP tool.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv2\n    id: SKILL-skill-gate\n    version: \"1.0.0\"\n    created: 2026-04-11T08:00:00Z\n    category: processkit\n    core: true\n    layer: 2\n    uses:\n      - skill: skill-finder\n        purpose: >\n          The mandatory first stop for any processkit domain task —\n          skill-gate enforces that skill-finder is consulted before\n          acting, not after.\n    provides:\n      primitives: []\n      mcp_tools: [acknowledge_contract, check_contract_acknowledged]\n      assets: []\n    commands:\n      - name: pk-build\n        args: \"\"\n        description: \"Run the project build command from the AGENTS.md pk-commands block\"\n      - name: pk-lint\n        args: \"\"\n        description: \"Run the project lint command from the AGENTS.md pk-commands block\"\n      - name: pk-test\n        args: \"\"\n        description: \"Run the project test command from the AGENTS.md pk-commands block\"\n      - name: pk-review\n        args: \"\"\n        description: \"Review the current branch against AGENTS.md conventions; report blockers \u002F warnings \u002F notes\"\n---\n\n# Skill Gate\n\n## Intro\n\nskill-gate is the enforcement layer that ensures agents consult the\nprocesskit skill catalog before acting on processkit entities or\n`context\u002F` files. It implements the **1% rule**: if there is even a 1%\nchance a processkit skill covers the current task, you must check\n`skill-finder` before doing anything else. It does not perform work\nitself — it ensures work is performed via the right skill.\n\n## Overview\n\n### The processkit Compliance Contract (v2)\n\nAGENTS.md ships a ToC of this contract; the authoritative rules live\nhere. Every session that touches processkit entities or `context\u002F`\nfiles is governed by all ten:\n\n1. **route_task before writes.** Call `route_task(task_description)`\n   before any `create_*`, `transition_*`, `link_*`, `record_*`, or\n   `open_*` tool call.\n2. **1% rule.** If there is even a 1% chance a processkit skill\n   applies, consult `skill-finder` (or call `find_skill`) before\n   acting.\n3. **Commit to entity creation in the same turn.** When you decide to\n   create a WorkItem, DecisionRecord, Note, or Artifact, call the tool\n   in the same turn — deferred entity creation is lost.\n4. **Write via MCP.** Write entities through MCP tools, not by\n   hand-editing files under `context\u002F` — hand edits bypass schema\n   validation, state-machine enforcement, and the event-log auto-entry.\n5. **Read via index.** Read entities through `index-management`\n   (`query_entities`, `get_entity`, `search_entities`) — do not use\n   `ls`, `grep`, or raw filesystem walks under `context\u002F`.\n6. **Log after state changes.** Log an event after any state change\n   that an MCP write did not already produce automatically.\n7. **Record accepted cross-cutting decisions.** After a cross-cutting\n   recommendation is accepted, call `record_decision` in the same turn.\n8. **Acknowledge decision language.** When the last five user messages\n   contain explicit decision language (approved \u002F decided \u002F ship it \u002F\n   let's go \u002F ok \u002F yes \u002F confirmed), either call `record_decision` in\n   the same turn or call `skip_decision_record(reason=...)` to\n   acknowledge the skip.\n9. **Templates are read-only.** Do not edit any file under\n   `context\u002Ftemplates\u002F` — it is a read-only upstream mirror used as a\n   diff baseline.\n10. **Don't hand-edit merged MCP config.** Edit the per-skill\n    `mcp-config.json` and let the installer re-merge.\n\nCompatibility shims in schemas, doctor checks, or harness adapters are\ntemporary migration aids only. The accepted end state is canonical\nprocesskit data: declared schema vocabulary, canonical IDs and\nfilenames, canonical directory layouts, and resolvable references.\nWhen a shim reveals drift, use the relevant processkit skill to create\nor apply a migration; do not treat grandfathering as a terminal\nresolution.\n\n### The 1% rule\n\nBefore any of the following actions, pause and apply the decision graph:\n\n- Editing or creating any file under `context\u002F`\n- Calling any processkit MCP tool (`create_*`, `transition_*`, `link_*`,\n  `record_*`, `open_*`)\n- Writing a WorkItem, Decision, Note, Artifact, or any other entity\n- Running a process the user described as a processkit task\n\n**The rule:** If there is even a **1% chance** a processkit skill\napplies to this task, you MUST check `skill-finder` before proceeding.\n\nThe threshold is deliberately near-zero. Do not rationalize past it.\n\n### Decision graph\n\n```\nIs this task related to processkit entities, context\u002F files,\nor any process the user described as a project-management task?\n│\n├─ YES (or unsure) ──→ Read skill-finder and identify the matching skill.\n│                       Load that skill. Work from it.\n│\n└─ NO ──────────────→ Proceed without skill-gate involvement.\n                       (Pure code edits, data analysis, etc. that have\n                       no processkit component do not need skill-gate.)\n```\n\n### What \"check skill-finder\" means\n\n1. Read `context\u002Fskills\u002Fprocesskit\u002Fskill-finder\u002FSKILL.md` — find the\n   trigger phrase that matches the current task.\n2. Load the identified skill's `SKILL.md`.\n3. Confirm from its **Intro** (3 sentences) that it is the right match.\n4. Work from that skill's **Overview** — not from general knowledge.\n\nIf `skill-finder` has an MCP server available (`find_skill` tool), call\nit instead of reading the file — it is faster and more reliable.\n\n### Pre-empting common rationalisations\n\nThese are the rationalizations agents use to skip skill-gate. Each one\nis wrong:\n\n| Rationalisation | Reality |\n|---|---|\n| \"I already know how to do this.\" | The skill may have processkit-specific entity paths, ID formats, MCP tools, and log conventions that general knowledge does not cover. Knowing the domain is not the same as knowing the processkit conventions for it. |\n| \"It's a simple edit — one line.\" | The state machine enforces valid transitions. A hand edit that bypasses the MCP server can put an entity in an invalid state, break the index, and skip the auto-log side effect. |\n| \"skill-finder won't have a match for this.\" | The catalog has 128+ skills. Check before assuming. If there genuinely is no match, `skill-builder` is the next step — not acting from general knowledge. |\n| \"The user told me exactly what to do.\" | User instructions describe intent, not process. The skill encodes the processkit-specific conventions for realizing that intent correctly. |\n| \"I've done this before in this session.\" | Skill-gate applies to each new task type, not just the first one. If the task domain shifts, check again. |\n\n### Mandatory skill-check task classes\n\nBefore starting any task in the following categories, call\n`find_skill(\u003Ctask-keyword>)` \u002F `list_skills()` (or\n`search_entities(kind=skill, text=\u003Ctask-keyword>)` via index-management)\n— even if you think you know the procedure:\n\n1. **Research ingestion** — importing notes, papers, or external\n   artefacts into the project context.\n2. **Artifact creation** — producing a new PRD, ADR, spec, brief, or\n   any structured output file.\n3. **Discussion management** — opening, advancing, or closing a\n   structured discussion thread.\n4. **Decision recording** — capturing a cross-cutting decision in a\n   DecisionRecord entity.\n5. **Backlog item creation** — adding a WorkItem, Epic, or task to\n   the backlog.\n6. **Quality audits** — reviewing a skill, process, schema, or\n   compliance artifact.\n\nThis list is not exhaustive — the 1% rule applies to every task, not\njust these six. The list names the classes where bypassing the catalog\nhas caused the most observed work-waste.\n\n### Escape hatch\n\nskill-gate does NOT apply when you are already operating inside a\nnamed processkit skill's workflow. If you loaded `workitem-management`\nand are following its Overview steps, you do not need to re-check\nskill-finder for each sub-action within that skill. Skill-gate is a\nsession-level gate, not a per-tool-call gate.\n\n## Gotchas\n\n- **Treating skill-gate as optional at session start.** It is not. If\n  this session may involve any processkit work, load skill-gate first.\n  The cost is one file read. The cost of skipping it is a hand edit\n  that bypasses schema validation, state-machine enforcement, index\n  sync, and the audit trail.\n- **Applying the 1% rule only to obvious processkit tasks.** \"Write a\n  standup\" and \"create a ticket\" are obvious. \"Quick note about this\n  idea\" (→ `note-management`), \"log that we deployed\" (→ `event-log`),\n  and \"check what's blocking us\" (→ `workitem-management`) are not\n  obvious but all have matching skills. When in doubt, check.\n- **Confusing skill-gate with skill-finder.** skill-gate enforces the\n  checking behaviour. skill-finder does the matching. They are distinct.\n  skill-gate tells you *when* to check; skill-finder tells you *what*\n  to use.\n- **Skipping skill-gate because the user said \"just edit the file.\"**\n  The user describes the outcome they want, not the correct processkit\n  process for achieving it. Hand-editing entity files bypasses the MCP\n  server's schema validation and state-machine enforcement. Use the MCP\n  tool unless the MCP server is explicitly unavailable.\n- **Forgetting that skill-gate applies to entity creation, not just\n  edits.** Writing a new YAML file under `context\u002Fworkitems\u002F` directly\n  is a hand edit. Even for new entities, use `create_workitem` (or the\n  relevant `create_*` tool) so the index stays in sync and the auto-log\n  fires.\n- **Applying the escape hatch too broadly.** The escape hatch covers\n  sub-actions *within* a skill you have already loaded and are actively\n  following. It does not cover switching to a different task type or\n  domain mid-session without re-checking.\n\n## Full reference\n\n### Why the threshold is 1%, not \"when clearly applicable\"\n\nA higher threshold — \"check skill-finder when the task is obviously a\nprocesskit task\" — fails because agents are systematically overconfident\nabout what they already know. The 1% rule removes the judgment call\nentirely. If there is any possibility, check. The marginal cost of an\nunnecessary skill-finder lookup is one file read (seconds). The cost of\nskipping it when it was needed is an out-of-sync index, an invalid\nentity state, or a missing audit trail entry.\n\n### Provider neutrality\n\nskill-gate is implemented entirely in prose — it makes no assumptions\nabout which AI harness loads it. The same behaviour applies whether the\nagent is Claude Code, Codex CLI, Cursor, or any other harness that\nreads SKILL.md files.\n\n### Relationship to AGENTS.md\n\nAGENTS.md carries the project-level instruction to load skill-gate\nat session start. skill-gate carries the enforcement logic. Keep them\nseparate: AGENTS.md says *when* to load skill-gate; skill-gate says\n*what to do* once loaded.\n\n### When skill-gate applies to non-processkit projects\n\nskill-gate is a processkit-specific skill. It is only meaningful in\nprojects that have processkit installed (i.e. that have a `context\u002F`\ndirectory with processkit entities). In projects without processkit,\nskill-gate should not be loaded.\n\n### Context directory layout\n\nAll processkit-installed material lives under `context\u002F`:\n\n```\ncontext\u002F\n├── skills\u002F         ← skill packages (SKILL.md, mcp\u002F, references\u002F, templates\u002F)\n├── schemas\u002F        ← JSON schemas for the core primitives\n├── state-machines\u002F ← state-machine definitions\n├── processes\u002F      ← process definitions (bug-fix, code-review, release, …)\n└── templates\u002F      ← immutable upstream mirror used as a diff baseline\n```\n\n`context\u002Ftemplates\u002Fprocesskit\u002F\u003Cversion>\u002F` is the verbatim upstream\nsnapshot. **Do not edit it.** Edit the live files at\n`context\u002Fskills\u002F\u003Cname>\u002FSKILL.md`, `context\u002Fprocesses\u002F\u003Cname>.md`, etc.,\ndirectly. Local edits are detected at the next sync via three-way diff\nagainst the templates mirror.\n\nEvery `context\u002F` subdirectory has an `INDEX.md`. **Read those first** —\ndo not slurp `context\u002Fskills\u002F` or any large directory at session start.\nLoad specific files only when the task demands it. This is the\nthree-level principle: start at Level 1 (intro), drop to Level 2\n(workflows) when the task narrows, drop to Level 3 (full reference) for\nedge cases.\n\n### Working with entities\n\nprocesskit models project state as **entities** — work items, decision\nrecords, discussions, log entries, scopes, gates, bindings, and so on.\nEach entity is a YAML file under `context\u002F\u003Ckind>s\u002F`, created lazily on\nfirst use. For each entity kind, processkit ships a schema at\n`context\u002Fschemas\u002F\u003Ckind>.yaml`, a state machine at\n`context\u002Fstate-machines\u002F\u003Ckind>.yaml`, and an MCP server at\n`context\u002Fskills\u002F\u003Ckind>-management\u002Fmcp\u002Fserver.py`.\n\n- **Read** entities through `index-management`: call `query_entities`,\n  `get_entity`, `search_entities` — not `ls`, `grep`, or filesystem\n  walks. The SQLite-backed index is faster, context-cheaper, and\n  reflects canonical state.\n- **Write** entities through the per-kind MCP servers:\n  `create_workitem` \u002F `transition_workitem`, `record_decision`, and so\n  on. Hand-editing entity files bypasses index updates and\n  state-machine validation. Reserve hand edits for cases the MCP tools\n  genuinely don't cover — and call `reindex()` after so the SQLite\n  index reflects the new state.\n- **Log an event** after any state change that an MCP write did not\n  already produce automatically (via `event-log`'s `log_event` tool).\n\n### MCP server wiring\n\nEach MCP-bearing skill ships its own `mcp\u002Fmcp-config.json` declaring\nhow to launch the server (typically `uv run …\u002Fserver.py`). Agent\nharnesses (Claude Code, Codex CLI, Cursor, …) read a single merged MCP\nconfig at startup, so the per-skill blocks must be merged and placed at\nthe harness-specific path. If an installer set the project up (for\nexample a managed devcontainer), the installer owns that wiring; if\nprocesskit was installed manually, the project owner merges the blocks\nby hand. Either way, MCP-bearing skills require **`uv`** and **Python\n≥ 3.10** on PATH — each `server.py` is a PEP 723 script and `uv run`\nresolves dependencies on first launch. Do not hand-edit the generated\nmerged harness config; edit per-skill `mcp-config.json` and let the\ninstaller re-merge.\n\n## How the gate is enforced\n\nskill-gate uses three complementary enforcement mechanisms. They are\nlayered, not alternatives — use whichever the harness supports.\n\n### (a) Prose fallback — the 1% rule\n\nThe primary enforcement mechanism is this SKILL.md itself. Every AI\nharness that loads SKILL.md receives the 1% rule in natural-language\nform: if there is even a 1% chance a processkit skill applies, check\n`skill-finder` first. Prose enforcement is provider-neutral — it works\non Claude Code, Codex CLI, Cursor, and any harness that reads SKILL.md\nfiles. It requires no MCP support. The cost is that it is advisory:\na harness that never loaded this file (or ignored it) has no hard\nbarrier.\n\n### (b) Tool-call acknowledgement via `acknowledge_contract()`\n\nWhen the harness speaks MCP, a stronger enforcement layer is available\nvia the `processkit-skill-gate` MCP server (`mcp\u002Fserver.py`). Call\n`acknowledge_contract(\"v1\")` once per session before any write-side\nprocesskit tool. On success the server writes a session marker file at:\n\n```\ncontext\u002F.state\u002Fskill-gate\u002Fsession-\u003CSESSION_ID>.ack\n```\n\nThe marker contains `contract_hash` and `acknowledged_at` (see\n`mcp\u002FSERVER.md` for the full schema). CI and harness hooks\n(`SteadyHand`'s `check_route_task_called.py`) read this directory to\nconfirm that a compliance acknowledgement was recorded for the session.\nThe companion tool `check_contract_acknowledged()` can be called by\nany write-side tool implementation to gate on acknowledgement before\nproceeding.\n\nSession ID is resolved from env var `PROCESSKIT_SESSION_ID` or\n`os.getpid()` — one MCP stdio server process equals one session.\n\n### (c) Optional tool-side preconditions on write tools (future)\n\nA planned follow-up (separate WorkItem) will wire `check_contract_acknowledged()`\nas a precondition check inside each write-side MCP tool\n(`create_workitem`, `record_decision`, `log_event`, etc.) so that\ncalling a write tool without a prior `acknowledge_contract()` in the\nsame session returns an error rather than proceeding silently. This is\nintentionally out of scope for the current implementation to allow the\nacknowledgement pattern to soak before hard-blocking write tools.\n","# Skill Gate\n\n## Intro\n\nskill-gate is the enforcement layer that ensures agents consult the\nprocesskit skill catalog before acting on processkit entities or\n`context\u002F` files. It implements the **1% rule**: if there is even a 1%\nchance a processkit skill covers the current task, you must check\n`skill-finder` before doing anything else. It does not perform work\nitself — it ensures work is performed via the right skill.\n\n## Overview\n\n### The processkit Compliance Contract (v2)\n\nAGENTS.md ships a ToC of this contract; the authoritative rules live\nhere. Every session that touches processkit entities or `context\u002F`\nfiles is governed by all ten:\n\n1. **route_task before writes.** Call `route_task(task_description)`\n   before any `create_*`, `transition_*`, `link_*`, `record_*`, or\n   `open_*` tool call.\n2. **1% rule.** If there is even a 1% chance a processkit skill\n   applies, consult `skill-finder` (or call `find_skill`) before\n   acting.\n3. **Commit to entity creation in the same turn.** When you decide to\n   create a WorkItem, DecisionRecord, Note, or Artifact, call the tool\n   in the same turn — deferred entity creation is lost.\n4. **Write via MCP.** Write entities through MCP tools, not by\n   hand-editing files under `context\u002F` — hand edits bypass schema\n   validation, state-machine enforcement, and the event-log auto-entry.\n5. **Read via index.** Read entities through `index-management`\n   (`query_entities`, `get_entity`, `search_entities`) — do not use\n   `ls`, `grep`, or raw filesystem walks under `context\u002F`.\n6. **Log after state changes.** Log an event after any state change\n   that an MCP write did not already produce automatically.\n7. **Record accepted cross-cutting decisions.** After a cross-cutting\n   recommendation is accepted, call `record_decision` in the same turn.\n8. **Acknowledge decision language.** When the last five user messages\n   contain explicit decision language (approved \u002F decided \u002F ship it \u002F\n   let's go \u002F ok \u002F yes \u002F confirmed), either call `record_decision` in\n   the same turn or call `skip_decision_record(reason=...)` to\n   acknowledge the skip.\n9. **Templates are read-only.** Do not edit any file under\n   `context\u002Ftemplates\u002F` — it is a read-only upstream mirror used as a\n   diff baseline.\n10. **Don't hand-edit merged MCP config.** Edit the per-skill\n    `mcp-config.json` and let the installer re-merge.\n\nCompatibility shims in schemas, doctor checks, or harness adapters are\ntemporary migration aids only. The accepted end state is canonical\nprocesskit data: declared schema vocabulary, canonical IDs and\nfilenames, canonical directory layouts, and resolvable references.\nWhen a shim reveals drift, use the relevant processkit skill to create\nor apply a migration; do not treat grandfathering as a terminal\nresolution.\n\n### The 1% rule\n\nBefore any of the following actions, pause and apply the decision graph:\n\n- Editing or creating any file under `context\u002F`\n- Calling any processkit MCP tool (`create_*`, `transition_*`, `link_*`,\n  `record_*`, `open_*`)\n- Writing a WorkItem, Decision, Note, Artifact, or any other entity\n- Running a process the user described as a processkit task\n\n**The rule:** If there is even a **1% chance** a processkit skill\napplies to this task, you MUST check `skill-finder` before proceeding.\n\nThe threshold is deliberately near-zero. Do not rationalize past it.\n\n### Decision graph\n\n```\nIs this task related to processkit entities, context\u002F files,\nor any process the user described as a project-management task?\n│\n├─ YES (or unsure) ──→ Read skill-finder and identify the matching skill.\n│                       Load that skill. Work from it.\n│\n└─ NO ──────────────→ Proceed without skill-gate involvement.\n                       (Pure code edits, data analysis, etc. that have\n                       no processkit component do not need skill-gate.)\n```\n\n### What \"check skill-finder\" means\n\n1. Read `context\u002Fskills\u002Fprocesskit\u002Fskill-finder\u002FSKILL.md` — find the\n   trigger phrase that matches the current task.\n2. Load the identified skill's `SKILL.md`.\n3. Confirm from its **Intro** (3 sentences) that it is the right match.\n4. Work from that skill's **Overview** — not from general knowledge.\n\nIf `skill-finder` has an MCP server available (`find_skill` tool), call\nit instead of reading the file — it is faster and more reliable.\n\n### Pre-empting common rationalisations\n\nThese are the rationalizations agents use to skip skill-gate. Each one\nis wrong:\n\n| Rationalisation | Reality |\n|---|---|\n| \"I already know how to do this.\" | The skill may have processkit-specific entity paths, ID formats, MCP tools, and log conventions that general knowledge does not cover. Knowing the domain is not the same as knowing the processkit conventions for it. |\n| \"It's a simple edit — one line.\" | The state machine enforces valid transitions. A hand edit that bypasses the MCP server can put an entity in an invalid state, break the index, and skip the auto-log side effect. |\n| \"skill-finder won't have a match for this.\" | The catalog has 128+ skills. Check before assuming. If there genuinely is no match, `skill-builder` is the next step — not acting from general knowledge. |\n| \"The user told me exactly what to do.\" | User instructions describe intent, not process. The skill encodes the processkit-specific conventions for realizing that intent correctly. |\n| \"I've done this before in this session.\" | Skill-gate applies to each new task type, not just the first one. If the task domain shifts, check again. |\n\n### Mandatory skill-check task classes\n\nBefore starting any task in the following categories, call\n`find_skill(\u003Ctask-keyword>)` \u002F `list_skills()` (or\n`search_entities(kind=skill, text=\u003Ctask-keyword>)` via index-management)\n— even if you think you know the procedure:\n\n1. **Research ingestion** — importing notes, papers, or external\n   artefacts into the project context.\n2. **Artifact creation** — producing a new PRD, ADR, spec, brief, or\n   any structured output file.\n3. **Discussion management** — opening, advancing, or closing a\n   structured discussion thread.\n4. **Decision recording** — capturing a cross-cutting decision in a\n   DecisionRecord entity.\n5. **Backlog item creation** — adding a WorkItem, Epic, or task to\n   the backlog.\n6. **Quality audits** — reviewing a skill, process, schema, or\n   compliance artifact.\n\nThis list is not exhaustive — the 1% rule applies to every task, not\njust these six. The list names the classes where bypassing the catalog\nhas caused the most observed work-waste.\n\n### Escape hatch\n\nskill-gate does NOT apply when you are already operating inside a\nnamed processkit skill's workflow. If you loaded `workitem-management`\nand are following its Overview steps, you do not need to re-check\nskill-finder for each sub-action within that skill. Skill-gate is a\nsession-level gate, not a per-tool-call gate.\n\n## Gotchas\n\n- **Treating skill-gate as optional at session start.** It is not. If\n  this session may involve any processkit work, load skill-gate first.\n  The cost is one file read. The cost of skipping it is a hand edit\n  that bypasses schema validation, state-machine enforcement, index\n  sync, and the audit trail.\n- **Applying the 1% rule only to obvious processkit tasks.** \"Write a\n  standup\" and \"create a ticket\" are obvious. \"Quick note about this\n  idea\" (→ `note-management`), \"log that we deployed\" (→ `event-log`),\n  and \"check what's blocking us\" (→ `workitem-management`) are not\n  obvious but all have matching skills. When in doubt, check.\n- **Confusing skill-gate with skill-finder.** skill-gate enforces the\n  checking behaviour. skill-finder does the matching. They are distinct.\n  skill-gate tells you *when* to check; skill-finder tells you *what*\n  to use.\n- **Skipping skill-gate because the user said \"just edit the file.\"**\n  The user describes the outcome they want, not the correct processkit\n  process for achieving it. Hand-editing entity files bypasses the MCP\n  server's schema validation and state-machine enforcement. Use the MCP\n  tool unless the MCP server is explicitly unavailable.\n- **Forgetting that skill-gate applies to entity creation, not just\n  edits.** Writing a new YAML file under `context\u002Fworkitems\u002F` directly\n  is a hand edit. Even for new entities, use `create_workitem` (or the\n  relevant `create_*` tool) so the index stays in sync and the auto-log\n  fires.\n- **Applying the escape hatch too broadly.** The escape hatch covers\n  sub-actions *within* a skill you have already loaded and are actively\n  following. It does not cover switching to a different task type or\n  domain mid-session without re-checking.\n\n## Full reference\n\n### Why the threshold is 1%, not \"when clearly applicable\"\n\nA higher threshold — \"check skill-finder when the task is obviously a\nprocesskit task\" — fails because agents are systematically overconfident\nabout what they already know. The 1% rule removes the judgment call\nentirely. If there is any possibility, check. The marginal cost of an\nunnecessary skill-finder lookup is one file read (seconds). The cost of\nskipping it when it was needed is an out-of-sync index, an invalid\nentity state, or a missing audit trail entry.\n\n### Provider neutrality\n\nskill-gate is implemented entirely in prose — it makes no assumptions\nabout which AI harness loads it. The same behaviour applies whether the\nagent is Claude Code, Codex CLI, Cursor, or any other harness that\nreads SKILL.md files.\n\n### Relationship to AGENTS.md\n\nAGENTS.md carries the project-level instruction to load skill-gate\nat session start. skill-gate carries the enforcement logic. Keep them\nseparate: AGENTS.md says *when* to load skill-gate; skill-gate says\n*what to do* once loaded.\n\n### When skill-gate applies to non-processkit projects\n\nskill-gate is a processkit-specific skill. It is only meaningful in\nprojects that have processkit installed (i.e. that have a `context\u002F`\ndirectory with processkit entities). In projects without processkit,\nskill-gate should not be loaded.\n\n### Context directory layout\n\nAll processkit-installed material lives under `context\u002F`:\n\n```\ncontext\u002F\n├── skills\u002F         ← skill packages (SKILL.md, mcp\u002F, references\u002F, templates\u002F)\n├── schemas\u002F        ← JSON schemas for the core primitives\n├── state-machines\u002F ← state-machine definitions\n├── processes\u002F      ← process definitions (bug-fix, code-review, release, …)\n└── templates\u002F      ← immutable upstream mirror used as a diff baseline\n```\n\n`context\u002Ftemplates\u002Fprocesskit\u002F\u003Cversion>\u002F` is the verbatim upstream\nsnapshot. **Do not edit it.** Edit the live files at\n`context\u002Fskills\u002F\u003Cname>\u002FSKILL.md`, `context\u002Fprocesses\u002F\u003Cname>.md`, etc.,\ndirectly. Local edits are detected at the next sync via three-way diff\nagainst the templates mirror.\n\nEvery `context\u002F` subdirectory has an `INDEX.md`. **Read those first** —\ndo not slurp `context\u002Fskills\u002F` or any large directory at session start.\nLoad specific files only when the task demands it. This is the\nthree-level principle: start at Level 1 (intro), drop to Level 2\n(workflows) when the task narrows, drop to Level 3 (full reference) for\nedge cases.\n\n### Working with entities\n\nprocesskit models project state as **entities** — work items, decision\nrecords, discussions, log entries, scopes, gates, bindings, and so on.\nEach entity is a YAML file under `context\u002F\u003Ckind>s\u002F`, created lazily on\nfirst use. For each entity kind, processkit ships a schema at\n`context\u002Fschemas\u002F\u003Ckind>.yaml`, a state machine at\n`context\u002Fstate-machines\u002F\u003Ckind>.yaml`, and an MCP server at\n`context\u002Fskills\u002F\u003Ckind>-management\u002Fmcp\u002Fserver.py`.\n\n- **Read** entities through `index-management`: call `query_entities`,\n  `get_entity`, `search_entities` — not `ls`, `grep`, or filesystem\n  walks. The SQLite-backed index is faster, context-cheaper, and\n  reflects canonical state.\n- **Write** entities through the per-kind MCP servers:\n  `create_workitem` \u002F `transition_workitem`, `record_decision`, and so\n  on. Hand-editing entity files bypasses index updates and\n  state-machine validation. Reserve hand edits for cases the MCP tools\n  genuinely don't cover — and call `reindex()` after so the SQLite\n  index reflects the new state.\n- **Log an event** after any state change that an MCP write did not\n  already produce automatically (via `event-log`'s `log_event` tool).\n\n### MCP server wiring\n\nEach MCP-bearing skill ships its own `mcp\u002Fmcp-config.json` declaring\nhow to launch the server (typically `uv run …\u002Fserver.py`). Agent\nharnesses (Claude Code, Codex CLI, Cursor, …) read a single merged MCP\nconfig at startup, so the per-skill blocks must be merged and placed at\nthe harness-specific path. If an installer set the project up (for\nexample a managed devcontainer), the installer owns that wiring; if\nprocesskit was installed manually, the project owner merges the blocks\nby hand. Either way, MCP-bearing skills require **`uv`** and **Python\n≥ 3.10** on PATH — each `server.py` is a PEP 723 script and `uv run`\nresolves dependencies on first launch. Do not hand-edit the generated\nmerged harness config; edit per-skill `mcp-config.json` and let the\ninstaller re-merge.\n\n## How the gate is enforced\n\nskill-gate uses three complementary enforcement mechanisms. They are\nlayered, not alternatives — use whichever the harness supports.\n\n### (a) Prose fallback — the 1% rule\n\nThe primary enforcement mechanism is this SKILL.md itself. Every AI\nharness that loads SKILL.md receives the 1% rule in natural-language\nform: if there is even a 1% chance a processkit skill applies, check\n`skill-finder` first. Prose enforcement is provider-neutral — it works\non Claude Code, Codex CLI, Cursor, and any harness that reads SKILL.md\nfiles. It requires no MCP support. The cost is that it is advisory:\na harness that never loaded this file (or ignored it) has no hard\nbarrier.\n\n### (b) Tool-call acknowledgement via `acknowledge_contract()`\n\nWhen the harness speaks MCP, a stronger enforcement layer is available\nvia the `processkit-skill-gate` MCP server (`mcp\u002Fserver.py`). Call\n`acknowledge_contract(\"v1\")` once per session before any write-side\nprocesskit tool. On success the server writes a session marker file at:\n\n```\ncontext\u002F.state\u002Fskill-gate\u002Fsession-\u003CSESSION_ID>.ack\n```\n\nThe marker contains `contract_hash` and `acknowledged_at` (see\n`mcp\u002FSERVER.md` for the full schema). CI and harness hooks\n(`SteadyHand`'s `check_route_task_called.py`) read this directory to\nconfirm that a compliance acknowledgement was recorded for the session.\nThe companion tool `check_contract_acknowledged()` can be called by\nany write-side tool implementation to gate on acknowledgement before\nproceeding.\n\nSession ID is resolved from env var `PROCESSKIT_SESSION_ID` or\n`os.getpid()` — one MCP stdio server process equals one session.\n\n### (c) Optional tool-side preconditions on write tools (future)\n\nA planned follow-up (separate WorkItem) will wire `check_contract_acknowledged()`\nas a precondition check inside each write-side MCP tool\n(`create_workitem`, `record_decision`, `log_event`, etc.) so that\ncalling a write tool without a prior `acknowledge_contract()` in the\nsame session returns an error rather than proceeding silently. This is\nintentionally out of scope for the current implementation to allow the\nacknowledgement pattern to soak before hard-blocking write tools.\n",{"name":5,"metadata":54,"description":87},{"processkit":55},{"id":56,"core":57,"uses":58,"layer":62,"created":63,"version":64,"category":65,"commands":66,"provides":80,"apiVersion":86},"SKILL-skill-gate",true,[59],{"skill":60,"purpose":61},"skill-finder","The mandatory first stop for any processkit domain task — skill-gate enforces that skill-finder is consulted before acting, not after.\n",2,1775894400000,"1.0.0","processkit",[67,71,74,77],{"args":68,"name":69,"description":70},"","pk-build","Run the project build command from the AGENTS.md pk-commands block",{"args":68,"name":72,"description":73},"pk-lint","Run the project lint command from the AGENTS.md pk-commands block",{"args":68,"name":75,"description":76},"pk-test","Run the project test command from the AGENTS.md pk-commands block",{"args":68,"name":78,"description":79},"pk-review","Review the current branch against AGENTS.md conventions; report blockers \u002F warnings \u002F notes",{"assets":81,"mcp_tools":82,"primitives":85},[],[83,84],"acknowledge_contract","check_contract_acknowledged",[],"processkit.projectious.work\u002Fv2","Session-start meta-skill that enforces the 1% rule: before any action\non a processkit entity or context\u002F file, if there is even a 1% chance\na processkit skill applies, you MUST check skill-finder first. Load\nthis skill at the start of every session that may involve processkit\nwork. Use when beginning a new task, when unsure which skill applies,\nor when you are about to edit context\u002F, create an entity, or run an\nMCP tool.\n","main","4876a92620ee792aac2ac9a1a806322d8a572367","archive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit","https:\u002F\u002Fprojectious-work.github.io\u002Fprocesskit\u002F","https:\u002F\u002Fgithub.com\u002Fprojectious-work","2026-11-11 23:24:18",{"source":8,"skillName":5,"commands":96,"prompt":106,"zipAvailable":57},[97,100,103],{"tool":98,"command":99},"npx","npx skills add projectious-work\u002Fprocesskit --skill skill-gate",{"tool":101,"command":102},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill skill-gate",{"tool":104,"command":105},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill skill-gate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002FSKILL.md",[108,114,118,124,128,132,135,139,143,149,153,157,161,165,169,173,177,181,185,189,193,197,201,205,209,213,217,221],{"path":109,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":112,"sourceHtmlUrl":113},"assets\u002Fcompliance-contract.md","ASSET","资产文件",4909,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fassets\u002Fcompliance-contract.md",{"path":115,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":116,"sourceHtmlUrl":117},"assets\u002Fpreauth.json",4592,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fassets\u002Fpreauth.json",{"path":119,"resourceType":120,"resourceTypeDesc":121,"sizeBytes":122,"sourceHtmlUrl":123},"commands\u002Fpk-build.md","REFERENCE","参考文档",523,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fcommands\u002Fpk-build.md",{"path":125,"resourceType":120,"resourceTypeDesc":121,"sizeBytes":126,"sourceHtmlUrl":127},"commands\u002Fpk-lint.md",521,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fcommands\u002Fpk-lint.md",{"path":129,"resourceType":120,"resourceTypeDesc":121,"sizeBytes":130,"sourceHtmlUrl":131},"commands\u002Fpk-review.md",755,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fcommands\u002Fpk-review.md",{"path":133,"resourceType":120,"resourceTypeDesc":121,"sizeBytes":126,"sourceHtmlUrl":134},"commands\u002Fpk-test.md","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fcommands\u002Fpk-test.md",{"path":136,"resourceType":120,"resourceTypeDesc":121,"sizeBytes":137,"sourceHtmlUrl":138},"mcp\u002Fmcp-config.json",203,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fmcp\u002Fmcp-config.json",{"path":140,"resourceType":120,"resourceTypeDesc":121,"sizeBytes":141,"sourceHtmlUrl":142},"mcp\u002FSERVER.md",5522,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fmcp\u002FSERVER.md",{"path":144,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":147,"sourceHtmlUrl":148},"mcp\u002Fserver.py","SCRIPT","脚本",14130,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fmcp\u002Fserver.py",{"path":150,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":151,"sourceHtmlUrl":152},"scripts\u002Fcheck_decision_captured.py",11551,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Fcheck_decision_captured.py",{"path":154,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":155,"sourceHtmlUrl":156},"scripts\u002Fcheck_entity_read.py",5921,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Fcheck_entity_read.py",{"path":158,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":159,"sourceHtmlUrl":160},"scripts\u002Fcheck_route_task_before_agent.py",5815,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Fcheck_route_task_before_agent.py",{"path":162,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":163,"sourceHtmlUrl":164},"scripts\u002Fcheck_route_task_called.py",11367,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Fcheck_route_task_called.py",{"path":166,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":167,"sourceHtmlUrl":168},"scripts\u002Fdecision_markers.py",4948,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Fdecision_markers.py",{"path":170,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":171,"sourceHtmlUrl":172},"scripts\u002Fdecision_sweeper.py",11938,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Fdecision_sweeper.py",{"path":174,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":175,"sourceHtmlUrl":176},"scripts\u002Femit_compliance_contract.py",6218,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Femit_compliance_contract.py",{"path":178,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":179,"sourceHtmlUrl":180},"scripts\u002Ffixtures\u002Fclaude-code-pre-tool-use.json",386,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Ffixtures\u002Fclaude-code-pre-tool-use.json",{"path":182,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":183,"sourceHtmlUrl":184},"scripts\u002Ffixtures\u002Fclaude-code-pretooluse-sample.json",400,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Ffixtures\u002Fclaude-code-pretooluse-sample.json",{"path":186,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":187,"sourceHtmlUrl":188},"scripts\u002Ffixtures\u002Fclaude-code-pretooluse-with-transcript.json",579,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Ffixtures\u002Fclaude-code-pretooluse-with-transcript.json",{"path":190,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":191,"sourceHtmlUrl":192},"scripts\u002Ffixtures\u002Fclaude-code-session-start.json",190,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Ffixtures\u002Fclaude-code-session-start.json",{"path":194,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":195,"sourceHtmlUrl":196},"scripts\u002Ffixtures\u002Fclaude-code-sessionend.json",461,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Ffixtures\u002Fclaude-code-sessionend.json",{"path":198,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":199,"sourceHtmlUrl":200},"scripts\u002Ffixtures\u002Fsample-transcript-no-decisions.jsonl",1808,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Ffixtures\u002Fsample-transcript-no-decisions.jsonl",{"path":202,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":203,"sourceHtmlUrl":204},"scripts\u002Ffixtures\u002Fsample-transcript-with-decisions.jsonl",2098,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Ffixtures\u002Fsample-transcript-with-decisions.jsonl",{"path":206,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":207,"sourceHtmlUrl":208},"scripts\u002Ffixtures\u002Fsample-transcript-with-poison-entries.jsonl",1562,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Ffixtures\u002Fsample-transcript-with-poison-entries.jsonl",{"path":210,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":211,"sourceHtmlUrl":212},"scripts\u002FREADME.md",4771,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002FREADME.md",{"path":214,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":215,"sourceHtmlUrl":216},"scripts\u002Frecord_decision_observer.py",3439,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Frecord_decision_observer.py",{"path":218,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":219,"sourceHtmlUrl":220},"scripts\u002Ftest_entity_read_and_agent_hooks.py",10262,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Ftest_entity_read_and_agent_hooks.py",{"path":222,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":223,"sourceHtmlUrl":224},"scripts\u002Ftest_hooks.py",27334,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-gate\u002Fscripts\u002Ftest_hooks.py",[226,233,240,246,268,287],{"skillNo":227,"name":228,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":229,"categories":230,"keywords":231,"publishedAt":232},"01M7665G2ED3624R3X93304265","standard-ui-design","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-ui-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":237,"categories":238,"keywords":239,"publishedAt":232},"01M76651QTC6W0HJ4AFW2MMR3V","standard-agent-use","Company standard for working with AI agents. Use when deciding what to delegate to agents, capturing open work, keeping agent memory or knowledge notes, improving an agent workflow, or introducing agent work in a team or for a client.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-use\u002FSKILL.md",[],[],{"skillNo":241,"name":242,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":243,"categories":244,"keywords":245,"publishedAt":232},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"skillNo":247,"name":248,"nameZh":6,"description":249,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":250,"categories":251,"keywords":253,"publishedAt":49},"01M6X5MTC89B4ZGXW3JVSQCPF8","skill-management","Manage Skill package manifests as v1 ontology entities.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-management\u002FSKILL.md",[252],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[254,255,256,257,46,258,43,259,260,261,262,263,248,264,265,266,267],"management","skill management","ontology","v1","as","transition","get","manage","update","alpha","list","package","skill package","manifests",{"skillNo":269,"name":270,"nameZh":6,"description":271,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":272,"categories":273,"keywords":275,"publishedAt":49},"01M6X5MCV74NHW5MEDNHZRF2C8","schema-management","Manage generated processkit schema contracts through deterministic MCP rebuild and inspection workflows.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fschema-management\u002FSKILL.md",[274],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[276,277,254,278,279,280,281,282,283,40,284,285,43,260,261,263,286],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","validation","deterministic","mode",{"skillNo":288,"name":289,"nameZh":6,"description":290,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":291,"categories":292,"keywords":293,"publishedAt":49},"01M6X5M5G6YJ96AMZGSCZJ1D13","proposition-management","Record claims, risks, beliefs, world facts, WSJF estimates, and assumptions through the Proposition interface.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fproposition-management\u002FSKILL.md",[],[294,254,295,296,46,297,298,299,43,260,300,301,262,302,263,303,304,305,306,307],"proposition management","proposition","interface","claims","record","world","creation","event","WSJF","index","updates","query","facts","log"]