[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75E1RXAN36CTX3K7RMJSZ2F":3,"skill-same:01M75E1RXAN36CTX3K7RMJSZ2F":49},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":48},"01M75E1RXAN36CTX3K7RMJSZ2F","sdd-archive",null,"Archive a completed SDD change by syncing delta specs. Trigger: orchestrator launches archive after implementation and verification.","AdrichDev\u002Fgru_orchestrator","AdrichDev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F172129260?v=4","01M75DR1Z03617FFA846AG5JJ6","Adrián Chozas","01M75DR1ZMXV62W49NBFHAMQBT",0,"MIT","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsdd-archive\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: sdd-archive\ndescription: \"Archive a completed SDD change by syncing delta specs. Trigger: orchestrator launches archive after implementation and verification.\"\ndisable-model-invocation: true\nuser-invocable: false\nlicense: MIT\nmetadata:\n  author: gentleman-programming\n  version: \"2.0\"\n  delegate_only: true\n---\n\n> **ORCHESTRATOR GATE**: If you loaded this skill via the `skill()` tool, you are\n> the ORCHESTRATOR — STOP. Do NOT execute these instructions inline. Delegate to\n> the dedicated `sdd-archive` sub-agent using your platform's delegation primitive\n> (e.g., `task(...)`, sub-agent invocation, etc.). This skill is for EXECUTORS\n> only.\n\n## Executor Override\n\nIf you ARE the `sdd-archive` sub-agent (NOT the orchestrator), the gate above does NOT apply to you. Continue with the phase work below. Do NOT delegate. Do NOT call the Skill tool. You are the executor — execute.\n\n\n## Language Domain Contract\n\nGenerated technical artifacts default to English. Do not inherit the user's conversational language or the active persona's regional voice for SDD artifacts unless the user explicitly requests that artifact language or the project convention requires it.\n\nIf Spanish technical artifacts are explicitly requested, use neutral\u002Fprofessional Spanish unless the user explicitly asks for a regional variant.\n\nPublic\u002Fcontextual comments follow the target context language by default. Explicit user language or tone overrides win; Spanish comments default to neutral\u002Fprofessional Spanish unless the user or target context clearly calls for regional tone.\n\n## Purpose\n\nYou are a sub-agent responsible for ARCHIVING. You merge delta specs into the main specs (source of truth), then move the change folder to the archive. You complete the SDD cycle.\n\n## What You Receive\n\nFrom the orchestrator:\n- Change name\n- Artifact store mode (`engram | openspec | hybrid | none`)\n- Structured status from `skills\u002F_shared\u002Fsdd-status-contract.md`, including artifact paths, task progress, dependency states, and actionContext\n- Any explicit intentional archive override text from the user\u002Forchestrator\n\n## Execution and Persistence Contract\n\n> Follow **Section B** (retrieval) and **Section C** (persistence) from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n\n- **engram**: Read `sdd\u002F{change-name}\u002Fproposal`, `sdd\u002F{change-name}\u002Fspec`, `sdd\u002F{change-name}\u002Fdesign`, `sdd\u002F{change-name}\u002Ftasks`, `sdd\u002F{change-name}\u002Fverify-report` (all required). Record all observation IDs in the archive report for traceability. Save as `sdd\u002F{change-name}\u002Farchive-report`.\n- **openspec**: Read and follow `skills\u002F_shared\u002Fopenspec-convention.md`. Perform merge and archive folder moves.\n- **hybrid**: Follow BOTH conventions — persist archive report to Engram (with observation IDs) AND perform filesystem merge + archive folder moves.\n- **none**: Return closure summary only. Do not perform archive file operations.\n\n### Task Completion Gate\n\n`sdd-apply` is responsible for marking completed tasks in the persisted tasks artifact. `sdd-archive` is responsible for validating that the persisted artifact reflects the final state before closing the cycle.\n\nBefore syncing specs or moving any archive folder, inspect the tasks artifact:\n\n- **engram**: read the full `sdd\u002F{change-name}\u002Ftasks` observation.\n- **openspec\u002Fhybrid**: read `openspec\u002Fchanges\u002F{change-name}\u002Ftasks.md`.\n\nIf any implementation task remains unchecked (`- [ ]`):\n\n1. STOP and return `blocked`; do not sync specs, move the change folder, or claim the SDD cycle is complete.\n2. Report that `sdd-apply` must be rerun or corrected so it marks completed tasks in the persisted tasks artifact.\n3. Only proceed if the orchestrator explicitly instructs you to reconcile stale checkboxes and `apply-progress`\u002F`verify-report` prove every unchecked task is complete. If you do this exceptional repair, record the exact reconciliation reason in the archive report.\n\nThe archived audit trail MUST NOT contain stale unchecked tasks for completed work. Internal todo state is not enough; the persisted SDD task artifact is the source of truth for completion visibility.\n\n### Strict-vs-OpenSpec Archive Policy\n\nOpenSpec permits archiving with incomplete artifacts or tasks after a user confirmation. gentle-ai is stricter by default:\n\n- Incomplete implementation tasks block archive unless they are stale checkboxes and apply-progress\u002Fverify-report prove completion.\n- CRITICAL issues in `verify-report` always block archive. Do not accept an override for CRITICAL verification issues.\n- `sdd-archive` does not own normal task completion. `sdd-apply` owns checkbox completion; archive may only perform exceptional mechanical reconciliation with proof from apply-progress and verify-report.\n- Missing proposal\u002Fspec\u002Fdesign artifacts should be reported. Archive may continue only when the user explicitly chooses an intentional partial archive and the archive report records what was missing.\n\n### Action Context Guard\n\n- If structured status reports `actionContext.mode: workspace-planning`, STOP. Do not move workspace changes into repo-local archives or edit linked repos.\n- If `allowedEditRoots` is present, archive operations must stay inside those roots.\n\n## What to Do\n\n### Step 1: Load Skills\nFollow **Section A** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n\n### Step 2: Sync Delta Specs to Main Specs\n\nDo not start this step until the **Task Completion Gate** above passes.\n\n**IF mode is `engram`:** Skip filesystem sync — artifacts live in Engram only. The archive report (Step 5) records all observation IDs for traceability.\n\n**IF mode is `none`:** Skip — no artifacts to sync.\n\n**IF mode is `openspec` or `hybrid`:** For each delta spec in `openspec\u002Fchanges\u002F{change-name}\u002Fspecs\u002F`:\n\n#### If Main Spec Exists (`openspec\u002Fspecs\u002F{domain}\u002Fspec.md`)\n\nRead the existing main spec and apply the delta:\n\n```\nFOR EACH SECTION in delta spec:\n├── ADDED Requirements → Append to main spec's Requirements section\n├── MODIFIED Requirements → Replace the matching requirement in main spec\n├── REMOVED Requirements → Delete the matching requirement from main spec after recording Reason\u002FMigration\n└── RENAMED Requirements → Rename the matching requirement while preserving scenarios unless the delta also modifies them\n```\n\n**Merge carefully:**\n- Match requirements by name (e.g., \"### Requirement: Session Expiration\")\n- Preserve all OTHER requirements that aren't in the delta\n- Maintain proper Markdown formatting and heading hierarchy\n- For REMOVED requirements, require `(Reason: ...)` and `(Migration: ...)` notes in the delta before deleting from main specs\n- For RENAMED requirements, require the old and new requirement names to be explicit\n\n#### If Main Spec Does NOT Exist\n\nThe delta spec IS a full spec (not a delta). Copy it directly:\n\n```bash\n# Copy new spec to main specs\nopenspec\u002Fchanges\u002F{change-name}\u002Fspecs\u002F{domain}\u002Fspec.md\n  → openspec\u002Fspecs\u002F{domain}\u002Fspec.md\n```\n\n### Step 3: Move to Archive\n\n**IF mode is `engram`:** Skip — there are no `openspec\u002F` directories to move. The archive report in Engram serves as the audit trail.\n\n**IF mode is `none`:** Skip — no filesystem operations.\n\n**IF mode is `openspec` or `hybrid`:** Move the entire change folder to archive with date prefix:\n\n```\nopenspec\u002Fchanges\u002F{change-name}\u002F\n  → openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-{change-name}\u002F\n```\n\nUse today's date in ISO format (e.g., `2026-02-16`).\n\n### Step 4: Verify Archive\n\n**IF mode is `openspec` or `hybrid`:** Confirm:\n- [ ] Main specs updated correctly\n- [ ] Change folder moved to archive\n- [ ] Archive contains all artifacts (proposal, specs, design, tasks)\n- [ ] Archived `tasks.md` has no unchecked implementation tasks, unless the orchestrator explicitly approved archive-time stale-checkbox reconciliation backed by apply-progress\u002Fverify-report proof\n- [ ] Active changes directory no longer has this change\n\n**IF mode is `engram`:** Confirm all artifact observation IDs are recorded in the archive report and the tasks observation has no unchecked implementation tasks unless the orchestrator explicitly approved archive-time stale-checkbox reconciliation backed by apply-progress\u002Fverify-report proof.\n\n**IF mode is `none`:** Skip verification — no persisted artifacts.\n\n### Step 5: Persist Archive Report\n\n**This step is MANDATORY — do NOT skip it.**\n\nFollow **Section C** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n- artifact: `archive-report`\n- topic_key: `sdd\u002F{change-name}\u002Farchive-report`\n- type: `architecture`\n\n### Step 6: Return Summary\n\nReturn to the orchestrator:\n\n```markdown\n## Change Archived\n\n**Change**: {change-name}\n**Archived to**: `openspec\u002Fchanges\u002Farchive\u002F{YYYY-MM-DD}-{change-name}\u002F` (openspec\u002Fhybrid) | Engram archive report (engram) | inline (none)\n\n### Specs Synced\n| Domain | Action | Details |\n|--------|--------|---------|\n| {domain} | Created\u002FUpdated | {N added, M modified, K removed requirements} |\n\n### Archive Contents\n- proposal.md ✅\n- specs\u002F ✅\n- design.md ✅\n- tasks.md ✅ ({N}\u002F{N} tasks complete)\n\n### Source of Truth Updated\nThe following specs now reflect the new behavior:\n- `openspec\u002Fspecs\u002F{domain}\u002Fspec.md`\n\n### SDD Cycle Complete\nThe change has been fully planned, implemented, verified, and archived.\nReady for the next change.\n```\n\n## Rules\n\n- NEVER archive a change that has CRITICAL issues in its verification report\n- If the user explicitly approves a non-critical partial archive or stale-checkbox reconciliation, record the exact reason in the archive report and mark the archive as intentional-with-warnings\n- NEVER archive completed work while `tasks.md` \u002F the tasks observation still shows stale unchecked implementation tasks\n- ALWAYS sync delta specs BEFORE moving to archive\n- When merging into existing specs, PRESERVE requirements not mentioned in the delta\n- Use ISO date format (YYYY-MM-DD) for archive folder prefix\n- If the merge would be destructive (removing large sections), WARN the orchestrator and ask for confirmation\n- The archive is an AUDIT TRAIL — never delete or modify archived changes\n- If `openspec\u002Fchanges\u002Farchive\u002F` doesn't exist, create it\n- Apply any `rules.archive` from `openspec\u002Fconfig.yaml`\n- Return envelope per **Section D** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n","> **ORCHESTRATOR GATE**: If you loaded this skill via the `skill()` tool, you are\n> the ORCHESTRATOR — STOP. Do NOT execute these instructions inline. Delegate to\n> the dedicated `sdd-archive` sub-agent using your platform's delegation primitive\n> (e.g., `task(...)`, sub-agent invocation, etc.). This skill is for EXECUTORS\n> only.\n\n## Executor Override\n\nIf you ARE the `sdd-archive` sub-agent (NOT the orchestrator), the gate above does NOT apply to you. Continue with the phase work below. Do NOT delegate. Do NOT call the Skill tool. You are the executor — execute.\n\n\n## Language Domain Contract\n\nGenerated technical artifacts default to English. Do not inherit the user's conversational language or the active persona's regional voice for SDD artifacts unless the user explicitly requests that artifact language or the project convention requires it.\n\nIf Spanish technical artifacts are explicitly requested, use neutral\u002Fprofessional Spanish unless the user explicitly asks for a regional variant.\n\nPublic\u002Fcontextual comments follow the target context language by default. Explicit user language or tone overrides win; Spanish comments default to neutral\u002Fprofessional Spanish unless the user or target context clearly calls for regional tone.\n\n## Purpose\n\nYou are a sub-agent responsible for ARCHIVING. You merge delta specs into the main specs (source of truth), then move the change folder to the archive. You complete the SDD cycle.\n\n## What You Receive\n\nFrom the orchestrator:\n- Change name\n- Artifact store mode (`engram | openspec | hybrid | none`)\n- Structured status from `skills\u002F_shared\u002Fsdd-status-contract.md`, including artifact paths, task progress, dependency states, and actionContext\n- Any explicit intentional archive override text from the user\u002Forchestrator\n\n## Execution and Persistence Contract\n\n> Follow **Section B** (retrieval) and **Section C** (persistence) from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n\n- **engram**: Read `sdd\u002F{change-name}\u002Fproposal`, `sdd\u002F{change-name}\u002Fspec`, `sdd\u002F{change-name}\u002Fdesign`, `sdd\u002F{change-name}\u002Ftasks`, `sdd\u002F{change-name}\u002Fverify-report` (all required). Record all observation IDs in the archive report for traceability. Save as `sdd\u002F{change-name}\u002Farchive-report`.\n- **openspec**: Read and follow `skills\u002F_shared\u002Fopenspec-convention.md`. Perform merge and archive folder moves.\n- **hybrid**: Follow BOTH conventions — persist archive report to Engram (with observation IDs) AND perform filesystem merge + archive folder moves.\n- **none**: Return closure summary only. Do not perform archive file operations.\n\n### Task Completion Gate\n\n`sdd-apply` is responsible for marking completed tasks in the persisted tasks artifact. `sdd-archive` is responsible for validating that the persisted artifact reflects the final state before closing the cycle.\n\nBefore syncing specs or moving any archive folder, inspect the tasks artifact:\n\n- **engram**: read the full `sdd\u002F{change-name}\u002Ftasks` observation.\n- **openspec\u002Fhybrid**: read `openspec\u002Fchanges\u002F{change-name}\u002Ftasks.md`.\n\nIf any implementation task remains unchecked (`- [ ]`):\n\n1. STOP and return `blocked`; do not sync specs, move the change folder, or claim the SDD cycle is complete.\n2. Report that `sdd-apply` must be rerun or corrected so it marks completed tasks in the persisted tasks artifact.\n3. Only proceed if the orchestrator explicitly instructs you to reconcile stale checkboxes and `apply-progress`\u002F`verify-report` prove every unchecked task is complete. If you do this exceptional repair, record the exact reconciliation reason in the archive report.\n\nThe archived audit trail MUST NOT contain stale unchecked tasks for completed work. Internal todo state is not enough; the persisted SDD task artifact is the source of truth for completion visibility.\n\n### Strict-vs-OpenSpec Archive Policy\n\nOpenSpec permits archiving with incomplete artifacts or tasks after a user confirmation. gentle-ai is stricter by default:\n\n- Incomplete implementation tasks block archive unless they are stale checkboxes and apply-progress\u002Fverify-report prove completion.\n- CRITICAL issues in `verify-report` always block archive. Do not accept an override for CRITICAL verification issues.\n- `sdd-archive` does not own normal task completion. `sdd-apply` owns checkbox completion; archive may only perform exceptional mechanical reconciliation with proof from apply-progress and verify-report.\n- Missing proposal\u002Fspec\u002Fdesign artifacts should be reported. Archive may continue only when the user explicitly chooses an intentional partial archive and the archive report records what was missing.\n\n### Action Context Guard\n\n- If structured status reports `actionContext.mode: workspace-planning`, STOP. Do not move workspace changes into repo-local archives or edit linked repos.\n- If `allowedEditRoots` is present, archive operations must stay inside those roots.\n\n## What to Do\n\n### Step 1: Load Skills\nFollow **Section A** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n\n### Step 2: Sync Delta Specs to Main Specs\n\nDo not start this step until the **Task Completion Gate** above passes.\n\n**IF mode is `engram`:** Skip filesystem sync — artifacts live in Engram only. The archive report (Step 5) records all observation IDs for traceability.\n\n**IF mode is `none`:** Skip — no artifacts to sync.\n\n**IF mode is `openspec` or `hybrid`:** For each delta spec in `openspec\u002Fchanges\u002F{change-name}\u002Fspecs\u002F`:\n\n#### If Main Spec Exists (`openspec\u002Fspecs\u002F{domain}\u002Fspec.md`)\n\nRead the existing main spec and apply the delta:\n\n```\nFOR EACH SECTION in delta spec:\n├── ADDED Requirements → Append to main spec's Requirements section\n├── MODIFIED Requirements → Replace the matching requirement in main spec\n├── REMOVED Requirements → Delete the matching requirement from main spec after recording Reason\u002FMigration\n└── RENAMED Requirements → Rename the matching requirement while preserving scenarios unless the delta also modifies them\n```\n\n**Merge carefully:**\n- Match requirements by name (e.g., \"### Requirement: Session Expiration\")\n- Preserve all OTHER requirements that aren't in the delta\n- Maintain proper Markdown formatting and heading hierarchy\n- For REMOVED requirements, require `(Reason: ...)` and `(Migration: ...)` notes in the delta before deleting from main specs\n- For RENAMED requirements, require the old and new requirement names to be explicit\n\n#### If Main Spec Does NOT Exist\n\nThe delta spec IS a full spec (not a delta). Copy it directly:\n\n```bash\n# Copy new spec to main specs\nopenspec\u002Fchanges\u002F{change-name}\u002Fspecs\u002F{domain}\u002Fspec.md\n  → openspec\u002Fspecs\u002F{domain}\u002Fspec.md\n```\n\n### Step 3: Move to Archive\n\n**IF mode is `engram`:** Skip — there are no `openspec\u002F` directories to move. The archive report in Engram serves as the audit trail.\n\n**IF mode is `none`:** Skip — no filesystem operations.\n\n**IF mode is `openspec` or `hybrid`:** Move the entire change folder to archive with date prefix:\n\n```\nopenspec\u002Fchanges\u002F{change-name}\u002F\n  → openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-{change-name}\u002F\n```\n\nUse today's date in ISO format (e.g., `2026-02-16`).\n\n### Step 4: Verify Archive\n\n**IF mode is `openspec` or `hybrid`:** Confirm:\n- [ ] Main specs updated correctly\n- [ ] Change folder moved to archive\n- [ ] Archive contains all artifacts (proposal, specs, design, tasks)\n- [ ] Archived `tasks.md` has no unchecked implementation tasks, unless the orchestrator explicitly approved archive-time stale-checkbox reconciliation backed by apply-progress\u002Fverify-report proof\n- [ ] Active changes directory no longer has this change\n\n**IF mode is `engram`:** Confirm all artifact observation IDs are recorded in the archive report and the tasks observation has no unchecked implementation tasks unless the orchestrator explicitly approved archive-time stale-checkbox reconciliation backed by apply-progress\u002Fverify-report proof.\n\n**IF mode is `none`:** Skip verification — no persisted artifacts.\n\n### Step 5: Persist Archive Report\n\n**This step is MANDATORY — do NOT skip it.**\n\nFollow **Section C** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n- artifact: `archive-report`\n- topic_key: `sdd\u002F{change-name}\u002Farchive-report`\n- type: `architecture`\n\n### Step 6: Return Summary\n\nReturn to the orchestrator:\n\n```markdown\n## Change Archived\n\n**Change**: {change-name}\n**Archived to**: `openspec\u002Fchanges\u002Farchive\u002F{YYYY-MM-DD}-{change-name}\u002F` (openspec\u002Fhybrid) | Engram archive report (engram) | inline (none)\n\n### Specs Synced\n| Domain | Action | Details |\n|--------|--------|---------|\n| {domain} | Created\u002FUpdated | {N added, M modified, K removed requirements} |\n\n### Archive Contents\n- proposal.md ✅\n- specs\u002F ✅\n- design.md ✅\n- tasks.md ✅ ({N}\u002F{N} tasks complete)\n\n### Source of Truth Updated\nThe following specs now reflect the new behavior:\n- `openspec\u002Fspecs\u002F{domain}\u002Fspec.md`\n\n### SDD Cycle Complete\nThe change has been fully planned, implemented, verified, and archived.\nReady for the next change.\n```\n\n## Rules\n\n- NEVER archive a change that has CRITICAL issues in its verification report\n- If the user explicitly approves a non-critical partial archive or stale-checkbox reconciliation, record the exact reason in the archive report and mark the archive as intentional-with-warnings\n- NEVER archive completed work while `tasks.md` \u002F the tasks observation still shows stale unchecked implementation tasks\n- ALWAYS sync delta specs BEFORE moving to archive\n- When merging into existing specs, PRESERVE requirements not mentioned in the delta\n- Use ISO date format (YYYY-MM-DD) for archive folder prefix\n- If the merge would be destructive (removing large sections), WARN the orchestrator and ask for confirmation\n- The archive is an AUDIT TRAIL — never delete or modify archived changes\n- If `openspec\u002Fchanges\u002Farchive\u002F` doesn't exist, create it\n- Apply any `rules.archive` from `openspec\u002Fconfig.yaml`\n- Return envelope per **Section D** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n",{"name":5,"license":15,"metadata":24,"description":7,"user-invocable":20,"disable-model-invocation":27},{"author":25,"version":26,"delegate_only":27},"gentleman-programming","2.0",true,"main","6745e47ba2ea20f71dce9a8303c332ef63ef43b6",".codex\u002Fskills\u002Fsdd-archive","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator","https:\u002F\u002Fgithub.com\u002FAdrichDev","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fadrichv\u002F","Software Junior Developer en continua formación y aprendizaje. Además , Trabajador social.\r\nIntentaré ir subiendo cositas!! \r\nFeliz día!!","2026-11-15 04:14:37",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":27},[38,41,44],{"tool":39,"command":40},"npx","npx skills add AdrichDev\u002Fgru_orchestrator --skill sdd-archive",{"tool":42,"command":43},"bunx","bunx skills add AdrichDev\u002Fgru_orchestrator --skill sdd-archive",{"tool":45,"command":46},"pnpm","pnpm dlx skills add AdrichDev\u002Fgru_orchestrator --skill sdd-archive","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsdd-archive\u002FSKILL.md",[],[50,57,62,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M75ED2J1WS4B52JV2Q0R01CB","invocable-skill","Run a security audit on the specified target. Use when asked to audit, scan, or assess security posture.","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002Fpackages\u002Fkernel\u002Fsrc\u002Fadapters\u002F__tests__\u002Fmock-ac-root\u002Fskills\u002Finvocable-skill\u002FSKILL.md",[],[],{"skillNo":58,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M75ECRCQFK3WY7Q990S3ZANF","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002Fpackages\u002Fkernel\u002Fsrc\u002Fadapters\u002F__tests__\u002Ffixtures-ac\u002Finvocable-skill\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M75ECJTFT8NZXFX0M95XHBGJ","work-unit-commits","Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fwork-unit-commits\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M75ECHC0CRV7MCB19WVAPQZN","skill-registry","Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path.","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fskill-registry\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M75ECFSPSZCFMA3BK74SN2M7","skill-improver","Trigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills.","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fskill-improver\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M75ECE874149EMN8ZEEMSAPM","skill-creator","Trigger: new skills, agent instructions, documenting AI usage patterns. Create LLM-first skills with valid frontmatter.","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[]]