[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6R2X1JF697QT8973K5SW5Z5":3,"skill-same:01M6R2X1JF697QT8973K5SW5Z5":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":13,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":66},"01M6R2X1JF697QT8973K5SW5Z5","ralph",null,"Convert PRDs to prd.json format for the Ralph autonomous agent system. Use when you have an existing PRD and need to convert it to Ralph's JSON format. Triggers on: convert this prd, turn this into ralph format, create prd.json from this, ralph json.","sixtycat2000-ctrl\u002Fgbrain-qmd","sixtycat2000-ctrl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263121306?v=4","01M6R2SPVP79P6Y6CC3HW4Y6GD","01M6R2SQ2MJXN4VVXWT7NQW9DD",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsixtycat2000-ctrl\u002Fgbrain-qmd\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fralph\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[5,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"use","when","agent system","Existing","for","true","you","it","triggers","autonomous agent","to prd","autonomous","format","json","convert","system","create prd","prd","create","2026-11-10 10:12:30",false,"---\nname: ralph\ndescription: \"Convert PRDs to prd.json format for the Ralph autonomous agent system. Use when you have an existing PRD and need to convert it to Ralph's JSON format. Triggers on: convert this prd, turn this into ralph format, create prd.json from this, ralph json.\"\nuser-invocable: true\n---\n\n# Ralph PRD Converter\n\nConverts existing PRDs to the prd.json format that Ralph uses for autonomous execution.\n\n---\n\n## The Job\n\nTake a PRD (markdown file or text) and convert it to `prd.json` in your ralph directory.\n\n---\n\n## Output Format\n\n```json\n{\n  \"project\": \"[Project Name]\",\n  \"branchName\": \"ralph\u002F[feature-name-kebab-case]\",\n  \"description\": \"[Feature description from PRD title\u002Fintro]\",\n  \"userStories\": [\n    {\n      \"id\": \"US-001\",\n      \"title\": \"[Story title]\",\n      \"description\": \"As a [user], I want [feature] so that [benefit]\",\n      \"acceptanceCriteria\": [\n        \"Criterion 1\",\n        \"Criterion 2\",\n        \"Typecheck passes\"\n      ],\n      \"priority\": 1,\n      \"passes\": false,\n      \"notes\": \"\"\n    }\n  ]\n}\n```\n\n---\n\n## Story Size: The Number One Rule\n\n**Each story must be completable in ONE Ralph iteration (one context window).**\n\nRalph spawns a fresh Amp instance per iteration with no memory of previous work. If a story is too big, the LLM runs out of context before finishing and produces broken code.\n\n### Right-sized stories:\n- Add a database column and migration\n- Add a UI component to an existing page\n- Update a server action with new logic\n- Add a filter dropdown to a list\n\n### Too big (split these):\n- \"Build the entire dashboard\" - Split into: schema, queries, UI components, filters\n- \"Add authentication\" - Split into: schema, middleware, login UI, session handling\n- \"Refactor the API\" - Split into one story per endpoint or pattern\n\n**Rule of thumb:** If you cannot describe the change in 2-3 sentences, it is too big.\n\n---\n\n## Story Ordering: Dependencies First\n\nStories execute in priority order. Earlier stories must not depend on later ones.\n\n**Correct order:**\n1. Schema\u002Fdatabase changes (migrations)\n2. Server actions \u002F backend logic\n3. UI components that use the backend\n4. Dashboard\u002Fsummary views that aggregate data\n\n**Wrong order:**\n1. UI component (depends on schema that does not exist yet)\n2. Schema change\n\n---\n\n## Acceptance Criteria: Must Be Verifiable\n\nEach criterion must be something Ralph can CHECK, not something vague.\n\n### Good criteria (verifiable):\n- \"Add `status` column to tasks table with default 'pending'\"\n- \"Filter dropdown has options: All, Active, Completed\"\n- \"Clicking delete shows confirmation dialog\"\n- \"Typecheck passes\"\n- \"Tests pass\"\n\n### Bad criteria (vague):\n- \"Works correctly\"\n- \"User can do X easily\"\n- \"Good UX\"\n- \"Handles edge cases\"\n\n### Always include as final criterion:\n```\n\"Typecheck passes\"\n```\n\nFor stories with testable logic, also include:\n```\n\"Tests pass\"\n```\n\n### For stories that change UI, also include:\n```\n\"Verify in browser using dev-browser skill\"\n```\n\nFrontend stories are NOT complete until visually verified. Ralph will use the dev-browser skill to navigate to the page, interact with the UI, and confirm changes work.\n\n---\n\n## Conversion Rules\n\n1. **Each user story becomes one JSON entry**\n2. **IDs**: Sequential (US-001, US-002, etc.)\n3. **Priority**: Based on dependency order, then document order\n4. **All stories**: `passes: false` and empty `notes`\n5. **branchName**: Derive from feature name, kebab-case, prefixed with `ralph\u002F`\n6. **Always add**: \"Typecheck passes\" to every story's acceptance criteria\n\n---\n\n## Splitting Large PRDs\n\nIf a PRD has big features, split them:\n\n**Original:**\n> \"Add user notification system\"\n\n**Split into:**\n1. US-001: Add notifications table to database\n2. US-002: Create notification service for sending notifications\n3. US-003: Add notification bell icon to header\n4. US-004: Create notification dropdown panel\n5. US-005: Add mark-as-read functionality\n6. US-006: Add notification preferences page\n\nEach is one focused change that can be completed and verified independently.\n\n---\n\n## Example\n\n**Input PRD:**\n```markdown\n# Task Status Feature\n\nAdd ability to mark tasks with different statuses.\n\n## Requirements\n- Toggle between pending\u002Fin-progress\u002Fdone on task list\n- Filter list by status\n- Show status badge on each task\n- Persist status in database\n```\n\n**Output prd.json:**\n```json\n{\n  \"project\": \"TaskApp\",\n  \"branchName\": \"ralph\u002Ftask-status\",\n  \"description\": \"Task Status Feature - Track task progress with status indicators\",\n  \"userStories\": [\n    {\n      \"id\": \"US-001\",\n      \"title\": \"Add status field to tasks table\",\n      \"description\": \"As a developer, I need to store task status in the database.\",\n      \"acceptanceCriteria\": [\n        \"Add status column: 'pending' | 'in_progress' | 'done' (default 'pending')\",\n        \"Generate and run migration successfully\",\n        \"Typecheck passes\"\n      ],\n      \"priority\": 1,\n      \"passes\": false,\n      \"notes\": \"\"\n    },\n    {\n      \"id\": \"US-002\",\n      \"title\": \"Display status badge on task cards\",\n      \"description\": \"As a user, I want to see task status at a glance.\",\n      \"acceptanceCriteria\": [\n        \"Each task card shows colored status badge\",\n        \"Badge colors: gray=pending, blue=in_progress, green=done\",\n        \"Typecheck passes\",\n        \"Verify in browser using dev-browser skill\"\n      ],\n      \"priority\": 2,\n      \"passes\": false,\n      \"notes\": \"\"\n    },\n    {\n      \"id\": \"US-003\",\n      \"title\": \"Add status toggle to task list rows\",\n      \"description\": \"As a user, I want to change task status directly from the list.\",\n      \"acceptanceCriteria\": [\n        \"Each row has status dropdown or toggle\",\n        \"Changing status saves immediately\",\n        \"UI updates without page refresh\",\n        \"Typecheck passes\",\n        \"Verify in browser using dev-browser skill\"\n      ],\n      \"priority\": 3,\n      \"passes\": false,\n      \"notes\": \"\"\n    },\n    {\n      \"id\": \"US-004\",\n      \"title\": \"Filter tasks by status\",\n      \"description\": \"As a user, I want to filter the list to see only certain statuses.\",\n      \"acceptanceCriteria\": [\n        \"Filter dropdown: All | Pending | In Progress | Done\",\n        \"Filter persists in URL params\",\n        \"Typecheck passes\",\n        \"Verify in browser using dev-browser skill\"\n      ],\n      \"priority\": 4,\n      \"passes\": false,\n      \"notes\": \"\"\n    }\n  ]\n}\n```\n\n---\n\n## Archiving Previous Runs\n\n**Before writing a new prd.json, check if there is an existing one from a different feature:**\n\n1. Read the current `prd.json` if it exists\n2. Check if `branchName` differs from the new feature's branch name\n3. If different AND `progress.txt` has content beyond the header:\n   - Create archive folder: `archive\u002FYYYY-MM-DD-feature-name\u002F`\n   - Copy current `prd.json` and `progress.txt` to archive\n   - Reset `progress.txt` with fresh header\n\n**The ralph.sh script handles this automatically** when you run it, but if you are manually updating prd.json between runs, archive first.\n\n---\n\n## Checklist Before Saving\n\nBefore writing prd.json, verify:\n\n- [ ] **Previous run archived** (if prd.json exists with different branchName, archive it first)\n- [ ] Each story is completable in one iteration (small enough)\n- [ ] Stories are ordered by dependency (schema to backend to UI)\n- [ ] Every story has \"Typecheck passes\" as criterion\n- [ ] UI stories have \"Verify in browser using dev-browser skill\" as criterion\n- [ ] Acceptance criteria are verifiable (not vague)\n- [ ] No story depends on a later story\n","# Ralph PRD Converter\n\nConverts existing PRDs to the prd.json format that Ralph uses for autonomous execution.\n\n---\n\n## The Job\n\nTake a PRD (markdown file or text) and convert it to `prd.json` in your ralph directory.\n\n---\n\n## Output Format\n\n```json\n{\n  \"project\": \"[Project Name]\",\n  \"branchName\": \"ralph\u002F[feature-name-kebab-case]\",\n  \"description\": \"[Feature description from PRD title\u002Fintro]\",\n  \"userStories\": [\n    {\n      \"id\": \"US-001\",\n      \"title\": \"[Story title]\",\n      \"description\": \"As a [user], I want [feature] so that [benefit]\",\n      \"acceptanceCriteria\": [\n        \"Criterion 1\",\n        \"Criterion 2\",\n        \"Typecheck passes\"\n      ],\n      \"priority\": 1,\n      \"passes\": false,\n      \"notes\": \"\"\n    }\n  ]\n}\n```\n\n---\n\n## Story Size: The Number One Rule\n\n**Each story must be completable in ONE Ralph iteration (one context window).**\n\nRalph spawns a fresh Amp instance per iteration with no memory of previous work. If a story is too big, the LLM runs out of context before finishing and produces broken code.\n\n### Right-sized stories:\n- Add a database column and migration\n- Add a UI component to an existing page\n- Update a server action with new logic\n- Add a filter dropdown to a list\n\n### Too big (split these):\n- \"Build the entire dashboard\" - Split into: schema, queries, UI components, filters\n- \"Add authentication\" - Split into: schema, middleware, login UI, session handling\n- \"Refactor the API\" - Split into one story per endpoint or pattern\n\n**Rule of thumb:** If you cannot describe the change in 2-3 sentences, it is too big.\n\n---\n\n## Story Ordering: Dependencies First\n\nStories execute in priority order. Earlier stories must not depend on later ones.\n\n**Correct order:**\n1. Schema\u002Fdatabase changes (migrations)\n2. Server actions \u002F backend logic\n3. UI components that use the backend\n4. Dashboard\u002Fsummary views that aggregate data\n\n**Wrong order:**\n1. UI component (depends on schema that does not exist yet)\n2. Schema change\n\n---\n\n## Acceptance Criteria: Must Be Verifiable\n\nEach criterion must be something Ralph can CHECK, not something vague.\n\n### Good criteria (verifiable):\n- \"Add `status` column to tasks table with default 'pending'\"\n- \"Filter dropdown has options: All, Active, Completed\"\n- \"Clicking delete shows confirmation dialog\"\n- \"Typecheck passes\"\n- \"Tests pass\"\n\n### Bad criteria (vague):\n- \"Works correctly\"\n- \"User can do X easily\"\n- \"Good UX\"\n- \"Handles edge cases\"\n\n### Always include as final criterion:\n```\n\"Typecheck passes\"\n```\n\nFor stories with testable logic, also include:\n```\n\"Tests pass\"\n```\n\n### For stories that change UI, also include:\n```\n\"Verify in browser using dev-browser skill\"\n```\n\nFrontend stories are NOT complete until visually verified. Ralph will use the dev-browser skill to navigate to the page, interact with the UI, and confirm changes work.\n\n---\n\n## Conversion Rules\n\n1. **Each user story becomes one JSON entry**\n2. **IDs**: Sequential (US-001, US-002, etc.)\n3. **Priority**: Based on dependency order, then document order\n4. **All stories**: `passes: false` and empty `notes`\n5. **branchName**: Derive from feature name, kebab-case, prefixed with `ralph\u002F`\n6. **Always add**: \"Typecheck passes\" to every story's acceptance criteria\n\n---\n\n## Splitting Large PRDs\n\nIf a PRD has big features, split them:\n\n**Original:**\n> \"Add user notification system\"\n\n**Split into:**\n1. US-001: Add notifications table to database\n2. US-002: Create notification service for sending notifications\n3. US-003: Add notification bell icon to header\n4. US-004: Create notification dropdown panel\n5. US-005: Add mark-as-read functionality\n6. US-006: Add notification preferences page\n\nEach is one focused change that can be completed and verified independently.\n\n---\n\n## Example\n\n**Input PRD:**\n```markdown\n# Task Status Feature\n\nAdd ability to mark tasks with different statuses.\n\n## Requirements\n- Toggle between pending\u002Fin-progress\u002Fdone on task list\n- Filter list by status\n- Show status badge on each task\n- Persist status in database\n```\n\n**Output prd.json:**\n```json\n{\n  \"project\": \"TaskApp\",\n  \"branchName\": \"ralph\u002Ftask-status\",\n  \"description\": \"Task Status Feature - Track task progress with status indicators\",\n  \"userStories\": [\n    {\n      \"id\": \"US-001\",\n      \"title\": \"Add status field to tasks table\",\n      \"description\": \"As a developer, I need to store task status in the database.\",\n      \"acceptanceCriteria\": [\n        \"Add status column: 'pending' | 'in_progress' | 'done' (default 'pending')\",\n        \"Generate and run migration successfully\",\n        \"Typecheck passes\"\n      ],\n      \"priority\": 1,\n      \"passes\": false,\n      \"notes\": \"\"\n    },\n    {\n      \"id\": \"US-002\",\n      \"title\": \"Display status badge on task cards\",\n      \"description\": \"As a user, I want to see task status at a glance.\",\n      \"acceptanceCriteria\": [\n        \"Each task card shows colored status badge\",\n        \"Badge colors: gray=pending, blue=in_progress, green=done\",\n        \"Typecheck passes\",\n        \"Verify in browser using dev-browser skill\"\n      ],\n      \"priority\": 2,\n      \"passes\": false,\n      \"notes\": \"\"\n    },\n    {\n      \"id\": \"US-003\",\n      \"title\": \"Add status toggle to task list rows\",\n      \"description\": \"As a user, I want to change task status directly from the list.\",\n      \"acceptanceCriteria\": [\n        \"Each row has status dropdown or toggle\",\n        \"Changing status saves immediately\",\n        \"UI updates without page refresh\",\n        \"Typecheck passes\",\n        \"Verify in browser using dev-browser skill\"\n      ],\n      \"priority\": 3,\n      \"passes\": false,\n      \"notes\": \"\"\n    },\n    {\n      \"id\": \"US-004\",\n      \"title\": \"Filter tasks by status\",\n      \"description\": \"As a user, I want to filter the list to see only certain statuses.\",\n      \"acceptanceCriteria\": [\n        \"Filter dropdown: All | Pending | In Progress | Done\",\n        \"Filter persists in URL params\",\n        \"Typecheck passes\",\n        \"Verify in browser using dev-browser skill\"\n      ],\n      \"priority\": 4,\n      \"passes\": false,\n      \"notes\": \"\"\n    }\n  ]\n}\n```\n\n---\n\n## Archiving Previous Runs\n\n**Before writing a new prd.json, check if there is an existing one from a different feature:**\n\n1. Read the current `prd.json` if it exists\n2. Check if `branchName` differs from the new feature's branch name\n3. If different AND `progress.txt` has content beyond the header:\n   - Create archive folder: `archive\u002FYYYY-MM-DD-feature-name\u002F`\n   - Copy current `prd.json` and `progress.txt` to archive\n   - Reset `progress.txt` with fresh header\n\n**The ralph.sh script handles this automatically** when you run it, but if you are manually updating prd.json between runs, archive first.\n\n---\n\n## Checklist Before Saving\n\nBefore writing prd.json, verify:\n\n- [ ] **Previous run archived** (if prd.json exists with different branchName, archive it first)\n- [ ] Each story is completable in one iteration (small enough)\n- [ ] Stories are ordered by dependency (schema to backend to UI)\n- [ ] Every story has \"Typecheck passes\" as criterion\n- [ ] UI stories have \"Verify in browser using dev-browser skill\" as criterion\n- [ ] Acceptance criteria are verifiable (not vague)\n- [ ] No story depends on a later story\n",{"name":5,"description":7,"user-invocable":47},true,"master","48f3da67113808a35b3721091cc58290a8c49ab4",".claude\u002Fskills\u002Fralph","https:\u002F\u002Fgithub.com\u002Fsixtycat2000-ctrl\u002Fgbrain-qmd","https:\u002F\u002Fgithub.com\u002Fsixtycat2000-ctrl","2026-04-26 19:27:01",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":47},[56,59,62],{"tool":57,"command":58},"npx","npx skills add sixtycat2000-ctrl\u002Fgbrain-qmd --skill ralph",{"tool":60,"command":61},"bunx","bunx skills add sixtycat2000-ctrl\u002Fgbrain-qmd --skill ralph",{"tool":63,"command":64},"pnpm","pnpm dlx skills add sixtycat2000-ctrl\u002Fgbrain-qmd --skill ralph","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsixtycat2000-ctrl\u002Fgbrain-qmd\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fralph\u002FSKILL.md",[],[68,93,127,151,174,195],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":42},"01M6R33ZFP10GVGJ7FX4GQWVK1","webhook-transforms","Generic framework for converting external events (SMS, meetings, social mentions)\ninto brain-ingestible signals. Define a transform function, register a webhook URL,\nand incoming events get processed through the brain pipeline.","https:\u002F\u002Fgithub.com\u002Fsixtycat2000-ctrl\u002Fgbrain-qmd\u002Fblob\u002Fmaster\u002Fskills\u002Fwebhook-transforms\u002FSKILL.md",[],[75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,28,27,92],"webhook","transforms","webhook transforms","search","pipeline","SET","page","meetings","up","social","signals","get","define","register","sms","event","URL","generic",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":110,"publishedAt":42},"01M6R33SCJAHZHG7HRN0JF29AB","testing","Skill validation framework. Validates every skill has SKILL.md with frontmatter,\nevery reference exists, every env var is declared. The testing contract for the\nskill system itself.","https:\u002F\u002Fgithub.com\u002Fsixtycat2000-ctrl\u002Fgbrain-qmd\u002Fblob\u002Fmaster\u002Fskills\u002Ftesting\u002FSKILL.md",[99,104,107],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":105,"categoryName":106,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":108,"categoryName":109,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000037","律师与法务",[95,111,112,113,78,114,38,115,116,117,118,119,120,121,122,123,124,125,126,27],"test","run","validation","health","check","health check","skill validation","validate skills","contract","tests","skill health","pages","env","false","test skills","with",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":42},"01M6R33DCE6RSA4YRCJ5H787E3","soul-audit","6-phase interactive interview that generates the agent's identity (SOUL.md),\nuser profile (USER.md), access control (ACCESS_POLICY.md), and operational\ncadence (HEARTBEAT.md). Re-runnable anytime to update any section.","https:\u002F\u002Fgithub.com\u002Fsixtycat2000-ctrl\u002Fgbrain-qmd\u002Fblob\u002Fmaster\u002Fskills\u002Fsoul-audit\u002FSKILL.md",[133],{"categoryNo":105,"categoryName":106,"taxonomyType":102,"taxonomyTypeDesc":103},[135,136,137,138,139,80,140,81,141,142,83,143,144,145,146,147,148,28,149,150],"audit","soul","soul audit","policy","customize","access","interactive","interview","personality","Access Control","cadence","SOUL.md","re","my agent","section","phase",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":42},"01M6R338GVZ1B8RCTWCEBG3SFS","smoke-test","Post-restart smoke tests + auto-fix for gbrain and OpenClaw environments.\nTests critical services, auto-fixes known issues, extensible via user-defined\ntest scripts in ~\u002F.gbrain\u002Fsmoke-tests.d\u002F*.sh.","https:\u002F\u002Fgithub.com\u002Fsixtycat2000-ctrl\u002Fgbrain-qmd\u002Fblob\u002Fmaster\u002Fskills\u002Fsmoke-test\u002FSKILL.md",[157],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},[111,159,160,161,162,112,163,164,165,166,167,120,168,169,170,28,27,171,172,173],"smoke","smoke test","openclaw","run smoke tests","issues","read","fix","auto","restart","critical","scripts","environments","fixes","break","auto-fix",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":42},"01M6R32XF94PR8S1G75S1FRZ94","skillpack-check","Run `gbrain skillpack-check` to produce an agent-readable JSON health report\nfor the gbrain install. Wraps `gbrain doctor` + `gbrain apply-migrations\n--list` so a host agent (your OpenClaw's morning-briefing, any OpenClaw cron)\ncan see at a glance whether the skillpack needs attention.\n\nUse when the user asks \"is gbrain healthy?\", when a cron fires a morning\ncheck, or proactively when something seems off (jobs not running, brain\nnot updating, autopilot silent).","https:\u002F\u002Fgithub.com\u002Fsixtycat2000-ctrl\u002Fgbrain-qmd\u002Fblob\u002Fmaster\u002Fskills\u002Fskillpack-check\u002FSKILL.md",[],[115,181,182,183,114,23,184,185,186,124,187,188,189,190,191,27,192,193,24,194],"skillpack check","doctor","produce","migrations","glance","attention","gbrain","host","healthy","briefing","can","apply","morning check","running",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":202,"publishedAt":42},"01M6R32RBQXAG40PM35VSA2Y8T","skillify","The meta skill. Turn any raw feature or script into a properly-skilled,\ntested, resolvable, evaled unit of agent-visible capability. Use when\nthe user says \"skillify this\", \"is this a skill?\", \"make this proper\",\nor after a new feature is built without the full skill infrastructure.\n\nPaired with `gbrain check-resolvable`, skillify gives a user-controllable\nequivalent of Hermes' auto-skill-creation: you build, skillify checks the\nchecklist, check-resolvable verifies nothing is orphaned. The human keeps\njudgment; the tooling keeps the checklist honest.","https:\u002F\u002Fgithub.com\u002Fsixtycat2000-ctrl\u002Fgbrain-qmd\u002Fblob\u002Fmaster\u002Fskills\u002Fskillify\u002FSKILL.md",[201],{"categoryNo":105,"categoryName":106,"taxonomyType":102,"taxonomyTypeDesc":103},[197,203,78,204,205,166,206,207,208,209,210,211,124,212,213,214,29,27,215,24],"infrastructure","Meta","list","evals","human","judgment","full","creation","feature","add","unit","make","capability"]