[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CSN38QV1MFD7ZPRFF2047W":3,"skill-same:01M6CSN38QV1MFD7ZPRFF2047W":62},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":14,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6CSN38QV1MFD7ZPRFF2047W","openspec-apply-change",null,"Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.","psacc\u002Fomnisess","psacc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F171010?v=4","01M6CSN1C11CTRR5G2Q0MCH0SE","Paolo Sacconier","01M6CSN1G116PZV68PYSN0WD31",1,"MIT","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenspec-apply-change\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"change","openspec apply change","openspec","cli","implement","tasks","start","continue","work","user","use","implementation","2026-11-10 10:12:30",false,"---\nname: openspec-apply-change\ndescription: Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.\nlicense: MIT\ncompatibility: Requires openspec CLI.\nmetadata:\n  author: openspec\n  version: \"1.0\"\n  generatedBy: \"1.1.1\"\n---\n\nImplement tasks from an OpenSpec change.\n\n**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.\n\n**Steps**\n\n1. **Select the change**\n\n   If a name is provided, use it. Otherwise:\n   - Infer from conversation context if the user mentioned a change\n   - Auto-select if only one active change exists\n   - If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select\n\n   Always announce: \"Using change: \u003Cname>\" and how to override (e.g., `\u002Fopsx:apply \u003Cother>`).\n\n2. **Check status to understand the schema**\n   ```bash\n   openspec status --change \"\u003Cname>\" --json\n   ```\n   Parse the JSON to understand:\n   - `schemaName`: The workflow being used (e.g., \"spec-driven\")\n   - Which artifact contains the tasks (typically \"tasks\" for spec-driven, check status for others)\n\n3. **Get apply instructions**\n\n   ```bash\n   openspec instructions apply --change \"\u003Cname>\" --json\n   ```\n\n   This returns:\n   - Context file paths (varies by schema - could be proposal\u002Fspecs\u002Fdesign\u002Ftasks or spec\u002Ftests\u002Fimplementation\u002Fdocs)\n   - Progress (total, complete, remaining)\n   - Task list with status\n   - Dynamic instruction based on current state\n\n   **Handle states:**\n   - If `state: \"blocked\"` (missing artifacts): show message, suggest using openspec-continue-change\n   - If `state: \"all_done\"`: congratulate, suggest archive\n   - Otherwise: proceed to implementation\n\n4. **Read context files**\n\n   Read the files listed in `contextFiles` from the apply instructions output.\n   The files depend on the schema being used:\n   - **spec-driven**: proposal, specs, design, tasks\n   - Other schemas: follow the contextFiles from CLI output\n\n5. **Show current progress**\n\n   Display:\n   - Schema being used\n   - Progress: \"N\u002FM tasks complete\"\n   - Remaining tasks overview\n   - Dynamic instruction from CLI\n\n6. **Implement tasks (loop until done or blocked)**\n\n   For each pending task:\n   - Show which task is being worked on\n   - Make the code changes required\n   - Keep changes minimal and focused\n   - Mark task complete in the tasks file: `- [ ]` → `- [x]`\n   - Continue to next task\n\n   **Pause if:**\n   - Task is unclear → ask for clarification\n   - Implementation reveals a design issue → suggest updating artifacts\n   - Error or blocker encountered → report and wait for guidance\n   - User interrupts\n\n7. **On completion or pause, show status**\n\n   Display:\n   - Tasks completed this session\n   - Overall progress: \"N\u002FM tasks complete\"\n   - If all done: suggest archive\n   - If paused: explain why and wait for guidance\n\n**Output During Implementation**\n\n```\n## Implementing: \u003Cchange-name> (schema: \u003Cschema-name>)\n\nWorking on task 3\u002F7: \u003Ctask description>\n[...implementation happening...]\n✓ Task complete\n\nWorking on task 4\u002F7: \u003Ctask description>\n[...implementation happening...]\n✓ Task complete\n```\n\n**Output On Completion**\n\n```\n## Implementation Complete\n\n**Change:** \u003Cchange-name>\n**Schema:** \u003Cschema-name>\n**Progress:** 7\u002F7 tasks complete ✓\n\n### Completed This Session\n- [x] Task 1\n- [x] Task 2\n...\n\nAll tasks complete! Ready to archive this change.\n```\n\n**Output On Pause (Issue Encountered)**\n\n```\n## Implementation Paused\n\n**Change:** \u003Cchange-name>\n**Schema:** \u003Cschema-name>\n**Progress:** 4\u002F7 tasks complete\n\n### Issue Encountered\n\u003Cdescription of the issue>\n\n**Options:**\n1. \u003Coption 1>\n2. \u003Coption 2>\n3. Other approach\n\nWhat would you like to do?\n```\n\n**Guardrails**\n- Keep going through tasks until done or blocked\n- Always read context files before starting (from the apply instructions output)\n- If task is ambiguous, pause and ask before implementing\n- If implementation reveals issues, pause and suggest artifact updates\n- Keep code changes minimal and scoped to each task\n- Update task checkbox immediately after completing each task\n- Pause on errors, blockers, or unclear requirements - don't guess\n- Use contextFiles from CLI output, don't assume specific file names\n\n**Fluid Workflow Integration**\n\nThis skill supports the \"actions on a change\" model:\n\n- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions\n- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly\n","Implement tasks from an OpenSpec change.\n\n**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.\n\n**Steps**\n\n1. **Select the change**\n\n   If a name is provided, use it. Otherwise:\n   - Infer from conversation context if the user mentioned a change\n   - Auto-select if only one active change exists\n   - If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select\n\n   Always announce: \"Using change: \u003Cname>\" and how to override (e.g., `\u002Fopsx:apply \u003Cother>`).\n\n2. **Check status to understand the schema**\n   ```bash\n   openspec status --change \"\u003Cname>\" --json\n   ```\n   Parse the JSON to understand:\n   - `schemaName`: The workflow being used (e.g., \"spec-driven\")\n   - Which artifact contains the tasks (typically \"tasks\" for spec-driven, check status for others)\n\n3. **Get apply instructions**\n\n   ```bash\n   openspec instructions apply --change \"\u003Cname>\" --json\n   ```\n\n   This returns:\n   - Context file paths (varies by schema - could be proposal\u002Fspecs\u002Fdesign\u002Ftasks or spec\u002Ftests\u002Fimplementation\u002Fdocs)\n   - Progress (total, complete, remaining)\n   - Task list with status\n   - Dynamic instruction based on current state\n\n   **Handle states:**\n   - If `state: \"blocked\"` (missing artifacts): show message, suggest using openspec-continue-change\n   - If `state: \"all_done\"`: congratulate, suggest archive\n   - Otherwise: proceed to implementation\n\n4. **Read context files**\n\n   Read the files listed in `contextFiles` from the apply instructions output.\n   The files depend on the schema being used:\n   - **spec-driven**: proposal, specs, design, tasks\n   - Other schemas: follow the contextFiles from CLI output\n\n5. **Show current progress**\n\n   Display:\n   - Schema being used\n   - Progress: \"N\u002FM tasks complete\"\n   - Remaining tasks overview\n   - Dynamic instruction from CLI\n\n6. **Implement tasks (loop until done or blocked)**\n\n   For each pending task:\n   - Show which task is being worked on\n   - Make the code changes required\n   - Keep changes minimal and focused\n   - Mark task complete in the tasks file: `- [ ]` → `- [x]`\n   - Continue to next task\n\n   **Pause if:**\n   - Task is unclear → ask for clarification\n   - Implementation reveals a design issue → suggest updating artifacts\n   - Error or blocker encountered → report and wait for guidance\n   - User interrupts\n\n7. **On completion or pause, show status**\n\n   Display:\n   - Tasks completed this session\n   - Overall progress: \"N\u002FM tasks complete\"\n   - If all done: suggest archive\n   - If paused: explain why and wait for guidance\n\n**Output During Implementation**\n\n```\n## Implementing: \u003Cchange-name> (schema: \u003Cschema-name>)\n\nWorking on task 3\u002F7: \u003Ctask description>\n[...implementation happening...]\n✓ Task complete\n\nWorking on task 4\u002F7: \u003Ctask description>\n[...implementation happening...]\n✓ Task complete\n```\n\n**Output On Completion**\n\n```\n## Implementation Complete\n\n**Change:** \u003Cchange-name>\n**Schema:** \u003Cschema-name>\n**Progress:** 7\u002F7 tasks complete ✓\n\n### Completed This Session\n- [x] Task 1\n- [x] Task 2\n...\n\nAll tasks complete! Ready to archive this change.\n```\n\n**Output On Pause (Issue Encountered)**\n\n```\n## Implementation Paused\n\n**Change:** \u003Cchange-name>\n**Schema:** \u003Cschema-name>\n**Progress:** 4\u002F7 tasks complete\n\n### Issue Encountered\n\u003Cdescription of the issue>\n\n**Options:**\n1. \u003Coption 1>\n2. \u003Coption 2>\n3. Other approach\n\nWhat would you like to do?\n```\n\n**Guardrails**\n- Keep going through tasks until done or blocked\n- Always read context files before starting (from the apply instructions output)\n- If task is ambiguous, pause and ask before implementing\n- If implementation reveals issues, pause and suggest artifact updates\n- Keep code changes minimal and scoped to each task\n- Update task checkbox immediately after completing each task\n- Pause on errors, blockers, or unclear requirements - don't guess\n- Use contextFiles from CLI output, don't assume specific file names\n\n**Fluid Workflow Integration**\n\nThis skill supports the \"actions on a change\" model:\n\n- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions\n- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly\n",{"name":5,"license":15,"metadata":36,"description":7,"compatibility":39},{"author":21,"version":37,"generatedBy":38},"1.0","1.1.1","Requires openspec CLI.","main","ef52a1fa5af69c0357cc554044ba40801d76165d",".claude\u002Fskills\u002Fopenspec-apply-change","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess","https:\u002F\u002Fgithub.com\u002Fpsacc","http:\u002F\u002Fpaolo.sacconier.net","brain in a jar","2026-11-05 20:37:15",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add psacc\u002Fomnisess --skill openspec-apply-change",{"tool":54,"command":55},"bunx","bunx skills add psacc\u002Fomnisess --skill openspec-apply-change",{"tool":57,"command":58},"pnpm","pnpm dlx skills add psacc\u002Fomnisess --skill openspec-apply-change","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenspec-apply-change\u002FSKILL.md",true,[],[63,88,111,127,144,159],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":31},"01M6CSQGP57Y6A3RC0FMQ7SNGK","stats","Show tool-call counts and file-I\u002FO activity from the transcript SQLite index.\nAggregates Read\u002FWrite\u002FEdit file paths, line counts, token usage, and error flags\nacross a time window (default 7d) or for a single session.\nUse this skill when asked which tools were used most, which files saw the most\nactivity, how many tokens were spent, or to inspect a single session's\ntool-call summary.\nTrigger phrases: \"session stats\", \"tool stats\", \"what tools did I use\",\n\"tool usage\", \"files touched\", \"token usage\", \"stats for last week\",\n\"summarize tool calls\", \"session tool breakdown\".","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002Fskills\u002Fomnisess-stats\u002FSKILL.md",[],[65,70,71,72,73,74,75,76,77,78,79,80,29,81,82,83,84,85,86,87],"transcript","file","sqlite","how","Bash","tool","json","read","write","edit","session","files","default","show","flags","call","aggregates","time",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":31},"01M6CSQDESFF8YP0CMETN519FE","skills-audit","Classify agent skills by usage tier (Keep \u002F Borderline \u002F Archive \u002F Unknown) using\nClaude Code session JSONL transcripts as the signal source. Read-only — never\nmodifies skills, sessions, or any file on disk.\nUse this skill when asked to audit skills, find unused skills, classify skills,\ncheck which skills get used, produce a skill usage report, or prune skills.\nTrigger phrases: \"audit skills\", \"find unused skills\", \"classify skills\",\n\"which skills do I use\", \"skill usage report\", \"prune skills\",\n\"what skills are unused\", \"skills I can remove\", \"trim my skill list\".\nOutput is a recommendation (Keep \u002F Borderline \u002F Archive) — acting on it is always\na manual step.","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002Fskills\u002Fomnisess-skills-audit\u002FSKILL.md",[],[95,96,97,98,99,100,71,101,74,102,103,104,105,106,80,107,29,108,109,110],"audit","skills audit","sessions","code","my skill","produce","disk","markdown","skill usage","archive","find","check","remove","never","only","do",{"skillNo":112,"name":83,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":31},"01M6CSQB2H38WJ1FKHFT4FQWQB","Show the full detail of a single AI coding session by its ID.\nSession IDs are in the format \u003Ctool>:\u003Cid> (e.g., claude:5c3f2742, cursor:a1b2c3d4).\nUse this skill when asked to show a specific session, inspect a session, read a session,\nor view the messages in a session.\nTrigger phrases: \"show session\", \"open session\", \"inspect session\", \"read session\",\n\"show me claude:5c3f2742\", \"view session details\", \"what happened in session\".","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002Fskills\u002Fomnisess-show\u002FSKILL.md",[],[83,117,118,119,120,74,75,121,122,77,123,124,80,29,125,126],"messages","ids","open","show me","format","coding","view","cursor","ai coding","me",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":31},"01M6CSQ8M3MRDR8EDAJMWZPKKH","search","Full-text search across all AI coding sessions (Claude Code, Cursor, Codex, GitHub Copilot CLI).\nUse this skill when asked to search sessions, find a conversation about a topic,\nlook up what was discussed in past sessions, or find sessions mentioning specific code or concepts.\nTrigger phrases: \"search sessions\", \"find sessions about\", \"look up in sessions\",\n\"what did I discuss about\", \"find conversation about\", \"search my history\".","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002Fskills\u002Fomnisess-search\u002FSKILL.md",[],[129,22,134,135,97,136,137,98,74,138,122,139,105,124,29,140,141,125,142,143],"github","codex","github copilot","copilot","text","history","up","look","conversation","query",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":31},"01M6CSQ5R6430D028Q9G41EX5Q","recap","Produce a structured markdown briefing of AI coding sessions for a given time window.\nGroups sessions by project and summarizes each group with intent, outcome, and status.\nUse this skill when asked to recap recent coding work, summarize today's sessions,\nshow what was worked on, or produce a daily\u002Fweekly session summary.\nTrigger phrases: \"recap\", \"what did I work on\", \"daily summary\", \"session summary\",\n\"summarize my sessions\", \"what sessions did I have today\", \"coding recap\".\nThis is the sessions-only public version — no Slack, Jira, or Granola integration.","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002Fskills\u002Fomnisess-recap\u002FSKILL.md",[],[146,151,97,152,100,74,102,153,27,154,80,29,155,109,156,125,157,83,158,87],"slack","session summary","work on","outcome","version","daily","intent","granola",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":31},"01M6CSQ31NYJNFR7R4WPYCXB2M","ps","Show live Claude Code and Codex sessions as a process tree, grouped by\nshared ancestor chain up to launchd. Covers Claude CLI sessions, Claude\nDesktop agent mode, and Codex sessions (CLI TUI + Codex.app threads).\nUse this skill when asked about the process tree, ancestor lineage, which\nterminal or tmux window a Claude or Codex session is running in, or what's\ncurrently running.\nTrigger phrases: \"process tree\", \"what's running\", \"lineage\", \"ancestor chain\",\n\"which terminal is my claude in\", \"tmux tree\", \"claude process tree\",\n\"codex process tree\", \"session lineage\".\nmacOS-only: on other platforms the command prints \"unsupported\" and exits 0.","https:\u002F\u002Fgithub.com\u002Fpsacc\u002Fomnisess\u002Fblob\u002Fmain\u002Fskills\u002Fomnisess-ps\u002FSKILL.md",[],[166,167,22,168,169,135,97,170,98,171,74,172,173,80,174,29,175,109,140,83],"PS","macos","terminal","tmux","desktop","lineage","tui","command","process","launchd"]