[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78V832TPDQXQR70DBB7X6CA":3,"skill-same:01M78V832TPDQXQR70DBB7X6CA":58},{"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":38,"commitSha":39,"skillDirectory":40,"forksCount":14,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M78V832TPDQXQR70DBB7X6CA","subagent-driven-development",null,"Use when executing implementation plans with independent tasks. Dispatches fresh delegate_task per task with two-stage review (spec compliance then code quality).","mfrancime\u002Ftrident-archive","mfrancime","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F577553?v=4","01M75NH5W71WGY7NTS8YQ6VP8G","verzillion_kram","01M75NH5WTX2HBXJZWRP4DGAPK",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmfrancime\u002Ftrident-archive\u002Fblob\u002Fmain\u002Frepos\u002Ftrident_hermes-agent_nousresearch_growing_ai\u002Fskills\u002Fsoftware-development\u002Fsubagent-driven-development\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: subagent-driven-development\ndescription: Use when executing implementation plans with independent tasks. Dispatches fresh delegate_task per task with two-stage review (spec compliance then code quality).\nversion: 1.1.0\nauthor: Hermes Agent (adapted from obra\u002Fsuperpowers)\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [delegation, subagent, implementation, workflow, parallel]\n    related_skills: [writing-plans, requesting-code-review, test-driven-development]\n---\n\n# Subagent-Driven Development\n\n## Overview\n\nExecute implementation plans by dispatching fresh subagents per task with systematic two-stage review.\n\n**Core principle:** Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration.\n\n## When to Use\n\nUse this skill when:\n- You have an implementation plan (from writing-plans skill or user requirements)\n- Tasks are mostly independent\n- Quality and spec compliance are important\n- You want automated review between tasks\n\n**vs. manual execution:**\n- Fresh context per task (no confusion from accumulated state)\n- Automated review process catches issues early\n- Consistent quality checks across all tasks\n- Subagents can ask questions before starting work\n\n## The Process\n\n### 1. Read and Parse Plan\n\nRead the plan file. Extract ALL tasks with their full text and context upfront. Create a todo list:\n\n```python\n# Read the plan\nread_file(\"docs\u002Fplans\u002Ffeature-plan.md\")\n\n# Create todo list with all tasks\ntodo([\n    {\"id\": \"task-1\", \"content\": \"Create User model with email field\", \"status\": \"pending\"},\n    {\"id\": \"task-2\", \"content\": \"Add password hashing utility\", \"status\": \"pending\"},\n    {\"id\": \"task-3\", \"content\": \"Create login endpoint\", \"status\": \"pending\"},\n])\n```\n\n**Key:** Read the plan ONCE. Extract everything. Don't make subagents read the plan file — provide the full task text directly in context.\n\n### 2. Per-Task Workflow\n\nFor EACH task in the plan:\n\n#### Step 1: Dispatch Implementer Subagent\n\nUse `delegate_task` with complete context:\n\n```python\ndelegate_task(\n    goal=\"Implement Task 1: Create User model with email and password_hash fields\",\n    context=\"\"\"\n    TASK FROM PLAN:\n    - Create: src\u002Fmodels\u002Fuser.py\n    - Add User class with email (str) and password_hash (str) fields\n    - Use bcrypt for password hashing\n    - Include __repr__ for debugging\n\n    FOLLOW TDD:\n    1. Write failing test in tests\u002Fmodels\u002Ftest_user.py\n    2. Run: pytest tests\u002Fmodels\u002Ftest_user.py -v (verify FAIL)\n    3. Write minimal implementation\n    4. Run: pytest tests\u002Fmodels\u002Ftest_user.py -v (verify PASS)\n    5. Run: pytest tests\u002F -q (verify no regressions)\n    6. Commit: git add -A && git commit -m \"feat: add User model with password hashing\"\n\n    PROJECT CONTEXT:\n    - Python 3.11, Flask app in src\u002Fapp.py\n    - Existing models in src\u002Fmodels\u002F\n    - Tests use pytest, run from project root\n    - bcrypt already in requirements.txt\n    \"\"\",\n    toolsets=['terminal', 'file']\n)\n```\n\n#### Step 2: Dispatch Spec Compliance Reviewer\n\nAfter the implementer completes, verify against the original spec:\n\n```python\ndelegate_task(\n    goal=\"Review if implementation matches the spec from the plan\",\n    context=\"\"\"\n    ORIGINAL TASK SPEC:\n    - Create src\u002Fmodels\u002Fuser.py with User class\n    - Fields: email (str), password_hash (str)\n    - Use bcrypt for password hashing\n    - Include __repr__\n\n    CHECK:\n    - [ ] All requirements from spec implemented?\n    - [ ] File paths match spec?\n    - [ ] Function signatures match spec?\n    - [ ] Behavior matches expected?\n    - [ ] Nothing extra added (no scope creep)?\n\n    OUTPUT: PASS or list of specific spec gaps to fix.\n    \"\"\",\n    toolsets=['file']\n)\n```\n\n**If spec issues found:** Fix gaps, then re-run spec review. Continue only when spec-compliant.\n\n#### Step 3: Dispatch Code Quality Reviewer\n\nAfter spec compliance passes:\n\n```python\ndelegate_task(\n    goal=\"Review code quality for Task 1 implementation\",\n    context=\"\"\"\n    FILES TO REVIEW:\n    - src\u002Fmodels\u002Fuser.py\n    - tests\u002Fmodels\u002Ftest_user.py\n\n    CHECK:\n    - [ ] Follows project conventions and style?\n    - [ ] Proper error handling?\n    - [ ] Clear variable\u002Ffunction names?\n    - [ ] Adequate test coverage?\n    - [ ] No obvious bugs or missed edge cases?\n    - [ ] No security issues?\n\n    OUTPUT FORMAT:\n    - Critical Issues: [must fix before proceeding]\n    - Important Issues: [should fix]\n    - Minor Issues: [optional]\n    - Verdict: APPROVED or REQUEST_CHANGES\n    \"\"\",\n    toolsets=['file']\n)\n```\n\n**If quality issues found:** Fix issues, re-review. Continue only when approved.\n\n#### Step 4: Mark Complete\n\n```python\ntodo([{\"id\": \"task-1\", \"content\": \"Create User model with email field\", \"status\": \"completed\"}], merge=True)\n```\n\n### 3. Final Review\n\nAfter ALL tasks are complete, dispatch a final integration reviewer:\n\n```python\ndelegate_task(\n    goal=\"Review the entire implementation for consistency and integration issues\",\n    context=\"\"\"\n    All tasks from the plan are complete. Review the full implementation:\n    - Do all components work together?\n    - Any inconsistencies between tasks?\n    - All tests passing?\n    - Ready for merge?\n    \"\"\",\n    toolsets=['terminal', 'file']\n)\n```\n\n### 4. Verify and Commit\n\n```bash\n# Run full test suite\npytest tests\u002F -q\n\n# Review all changes\ngit diff --stat\n\n# Final commit if needed\ngit add -A && git commit -m \"feat: complete [feature name] implementation\"\n```\n\n## Task Granularity\n\n**Each task = 2-5 minutes of focused work.**\n\n**Too big:**\n- \"Implement user authentication system\"\n\n**Right size:**\n- \"Create User model with email and password fields\"\n- \"Add password hashing function\"\n- \"Create login endpoint\"\n- \"Add JWT token generation\"\n- \"Create registration endpoint\"\n\n## Red Flags — Never Do These\n\n- Start implementation without a plan\n- Skip reviews (spec compliance OR code quality)\n- Proceed with unfixed critical\u002Fimportant issues\n- Dispatch multiple implementation subagents for tasks that touch the same files\n- Make subagent read the plan file (provide full text in context instead)\n- Skip scene-setting context (subagent needs to understand where the task fits)\n- Ignore subagent questions (answer before letting them proceed)\n- Accept \"close enough\" on spec compliance\n- Skip review loops (reviewer found issues → implementer fixes → review again)\n- Let implementer self-review replace actual review (both are needed)\n- **Start code quality review before spec compliance is PASS** (wrong order)\n- Move to next task while either review has open issues\n\n## Handling Issues\n\n### If Subagent Asks Questions\n\n- Answer clearly and completely\n- Provide additional context if needed\n- Don't rush them into implementation\n\n### If Reviewer Finds Issues\n\n- Implementer subagent (or a new one) fixes them\n- Reviewer reviews again\n- Repeat until approved\n- Don't skip the re-review\n\n### If Subagent Fails a Task\n\n- Dispatch a new fix subagent with specific instructions about what went wrong\n- Don't try to fix manually in the controller session (context pollution)\n\n## Efficiency Notes\n\n**Why fresh subagent per task:**\n- Prevents context pollution from accumulated state\n- Each subagent gets clean, focused context\n- No confusion from prior tasks' code or reasoning\n\n**Why two-stage review:**\n- Spec review catches under\u002Fover-building early\n- Quality review ensures the implementation is well-built\n- Catches issues before they compound across tasks\n\n**Cost trade-off:**\n- More subagent invocations (implementer + 2 reviewers per task)\n- But catches issues early (cheaper than debugging compounded problems later)\n\n## Integration with Other Skills\n\n### With writing-plans\n\nThis skill EXECUTES plans created by the writing-plans skill:\n1. User requirements → writing-plans → implementation plan\n2. Implementation plan → subagent-driven-development → working code\n\n### With test-driven-development\n\nImplementer subagents should follow TDD:\n1. Write failing test first\n2. Implement minimal code\n3. Verify test passes\n4. Commit\n\nInclude TDD instructions in every implementer context.\n\n### With requesting-code-review\n\nThe two-stage review process IS the code review. For final integration review, use the requesting-code-review skill's review dimensions.\n\n### With systematic-debugging\n\nIf a subagent encounters bugs during implementation:\n1. Follow systematic-debugging process\n2. Find root cause before fixing\n3. Write regression test\n4. Resume implementation\n\n## Example Workflow\n\n```\n[Read plan: docs\u002Fplans\u002Fauth-feature.md]\n[Create todo list with 5 tasks]\n\n--- Task 1: Create User model ---\n[Dispatch implementer subagent]\n  Implementer: \"Should email be unique?\"\n  You: \"Yes, email must be unique\"\n  Implementer: Implemented, 3\u002F3 tests passing, committed.\n\n[Dispatch spec reviewer]\n  Spec reviewer: ✅ PASS — all requirements met\n\n[Dispatch quality reviewer]\n  Quality reviewer: ✅ APPROVED — clean code, good tests\n\n[Mark Task 1 complete]\n\n--- Task 2: Password hashing ---\n[Dispatch implementer subagent]\n  Implementer: No questions, implemented, 5\u002F5 tests passing.\n\n[Dispatch spec reviewer]\n  Spec reviewer: ❌ Missing: password strength validation (spec says \"min 8 chars\")\n\n[Implementer fixes]\n  Implementer: Added validation, 7\u002F7 tests passing.\n\n[Dispatch spec reviewer again]\n  Spec reviewer: ✅ PASS\n\n[Dispatch quality reviewer]\n  Quality reviewer: Important: Magic number 8, extract to constant\n  Implementer: Extracted MIN_PASSWORD_LENGTH constant\n  Quality reviewer: ✅ APPROVED\n\n[Mark Task 2 complete]\n\n... (continue for all tasks)\n\n[After all tasks: dispatch final integration reviewer]\n[Run full test suite: all passing]\n[Done!]\n```\n\n## Remember\n\n```\nFresh subagent per task\nTwo-stage review every time\nSpec compliance FIRST\nCode quality SECOND\nNever skip reviews\nCatch issues early\n```\n\n**Quality is not an accident. It's the result of systematic process.**\n","# Subagent-Driven Development\n\n## Overview\n\nExecute implementation plans by dispatching fresh subagents per task with systematic two-stage review.\n\n**Core principle:** Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration.\n\n## When to Use\n\nUse this skill when:\n- You have an implementation plan (from writing-plans skill or user requirements)\n- Tasks are mostly independent\n- Quality and spec compliance are important\n- You want automated review between tasks\n\n**vs. manual execution:**\n- Fresh context per task (no confusion from accumulated state)\n- Automated review process catches issues early\n- Consistent quality checks across all tasks\n- Subagents can ask questions before starting work\n\n## The Process\n\n### 1. Read and Parse Plan\n\nRead the plan file. Extract ALL tasks with their full text and context upfront. Create a todo list:\n\n```python\n# Read the plan\nread_file(\"docs\u002Fplans\u002Ffeature-plan.md\")\n\n# Create todo list with all tasks\ntodo([\n    {\"id\": \"task-1\", \"content\": \"Create User model with email field\", \"status\": \"pending\"},\n    {\"id\": \"task-2\", \"content\": \"Add password hashing utility\", \"status\": \"pending\"},\n    {\"id\": \"task-3\", \"content\": \"Create login endpoint\", \"status\": \"pending\"},\n])\n```\n\n**Key:** Read the plan ONCE. Extract everything. Don't make subagents read the plan file — provide the full task text directly in context.\n\n### 2. Per-Task Workflow\n\nFor EACH task in the plan:\n\n#### Step 1: Dispatch Implementer Subagent\n\nUse `delegate_task` with complete context:\n\n```python\ndelegate_task(\n    goal=\"Implement Task 1: Create User model with email and password_hash fields\",\n    context=\"\"\"\n    TASK FROM PLAN:\n    - Create: src\u002Fmodels\u002Fuser.py\n    - Add User class with email (str) and password_hash (str) fields\n    - Use bcrypt for password hashing\n    - Include __repr__ for debugging\n\n    FOLLOW TDD:\n    1. Write failing test in tests\u002Fmodels\u002Ftest_user.py\n    2. Run: pytest tests\u002Fmodels\u002Ftest_user.py -v (verify FAIL)\n    3. Write minimal implementation\n    4. Run: pytest tests\u002Fmodels\u002Ftest_user.py -v (verify PASS)\n    5. Run: pytest tests\u002F -q (verify no regressions)\n    6. Commit: git add -A && git commit -m \"feat: add User model with password hashing\"\n\n    PROJECT CONTEXT:\n    - Python 3.11, Flask app in src\u002Fapp.py\n    - Existing models in src\u002Fmodels\u002F\n    - Tests use pytest, run from project root\n    - bcrypt already in requirements.txt\n    \"\"\",\n    toolsets=['terminal', 'file']\n)\n```\n\n#### Step 2: Dispatch Spec Compliance Reviewer\n\nAfter the implementer completes, verify against the original spec:\n\n```python\ndelegate_task(\n    goal=\"Review if implementation matches the spec from the plan\",\n    context=\"\"\"\n    ORIGINAL TASK SPEC:\n    - Create src\u002Fmodels\u002Fuser.py with User class\n    - Fields: email (str), password_hash (str)\n    - Use bcrypt for password hashing\n    - Include __repr__\n\n    CHECK:\n    - [ ] All requirements from spec implemented?\n    - [ ] File paths match spec?\n    - [ ] Function signatures match spec?\n    - [ ] Behavior matches expected?\n    - [ ] Nothing extra added (no scope creep)?\n\n    OUTPUT: PASS or list of specific spec gaps to fix.\n    \"\"\",\n    toolsets=['file']\n)\n```\n\n**If spec issues found:** Fix gaps, then re-run spec review. Continue only when spec-compliant.\n\n#### Step 3: Dispatch Code Quality Reviewer\n\nAfter spec compliance passes:\n\n```python\ndelegate_task(\n    goal=\"Review code quality for Task 1 implementation\",\n    context=\"\"\"\n    FILES TO REVIEW:\n    - src\u002Fmodels\u002Fuser.py\n    - tests\u002Fmodels\u002Ftest_user.py\n\n    CHECK:\n    - [ ] Follows project conventions and style?\n    - [ ] Proper error handling?\n    - [ ] Clear variable\u002Ffunction names?\n    - [ ] Adequate test coverage?\n    - [ ] No obvious bugs or missed edge cases?\n    - [ ] No security issues?\n\n    OUTPUT FORMAT:\n    - Critical Issues: [must fix before proceeding]\n    - Important Issues: [should fix]\n    - Minor Issues: [optional]\n    - Verdict: APPROVED or REQUEST_CHANGES\n    \"\"\",\n    toolsets=['file']\n)\n```\n\n**If quality issues found:** Fix issues, re-review. Continue only when approved.\n\n#### Step 4: Mark Complete\n\n```python\ntodo([{\"id\": \"task-1\", \"content\": \"Create User model with email field\", \"status\": \"completed\"}], merge=True)\n```\n\n### 3. Final Review\n\nAfter ALL tasks are complete, dispatch a final integration reviewer:\n\n```python\ndelegate_task(\n    goal=\"Review the entire implementation for consistency and integration issues\",\n    context=\"\"\"\n    All tasks from the plan are complete. Review the full implementation:\n    - Do all components work together?\n    - Any inconsistencies between tasks?\n    - All tests passing?\n    - Ready for merge?\n    \"\"\",\n    toolsets=['terminal', 'file']\n)\n```\n\n### 4. Verify and Commit\n\n```bash\n# Run full test suite\npytest tests\u002F -q\n\n# Review all changes\ngit diff --stat\n\n# Final commit if needed\ngit add -A && git commit -m \"feat: complete [feature name] implementation\"\n```\n\n## Task Granularity\n\n**Each task = 2-5 minutes of focused work.**\n\n**Too big:**\n- \"Implement user authentication system\"\n\n**Right size:**\n- \"Create User model with email and password fields\"\n- \"Add password hashing function\"\n- \"Create login endpoint\"\n- \"Add JWT token generation\"\n- \"Create registration endpoint\"\n\n## Red Flags — Never Do These\n\n- Start implementation without a plan\n- Skip reviews (spec compliance OR code quality)\n- Proceed with unfixed critical\u002Fimportant issues\n- Dispatch multiple implementation subagents for tasks that touch the same files\n- Make subagent read the plan file (provide full text in context instead)\n- Skip scene-setting context (subagent needs to understand where the task fits)\n- Ignore subagent questions (answer before letting them proceed)\n- Accept \"close enough\" on spec compliance\n- Skip review loops (reviewer found issues → implementer fixes → review again)\n- Let implementer self-review replace actual review (both are needed)\n- **Start code quality review before spec compliance is PASS** (wrong order)\n- Move to next task while either review has open issues\n\n## Handling Issues\n\n### If Subagent Asks Questions\n\n- Answer clearly and completely\n- Provide additional context if needed\n- Don't rush them into implementation\n\n### If Reviewer Finds Issues\n\n- Implementer subagent (or a new one) fixes them\n- Reviewer reviews again\n- Repeat until approved\n- Don't skip the re-review\n\n### If Subagent Fails a Task\n\n- Dispatch a new fix subagent with specific instructions about what went wrong\n- Don't try to fix manually in the controller session (context pollution)\n\n## Efficiency Notes\n\n**Why fresh subagent per task:**\n- Prevents context pollution from accumulated state\n- Each subagent gets clean, focused context\n- No confusion from prior tasks' code or reasoning\n\n**Why two-stage review:**\n- Spec review catches under\u002Fover-building early\n- Quality review ensures the implementation is well-built\n- Catches issues before they compound across tasks\n\n**Cost trade-off:**\n- More subagent invocations (implementer + 2 reviewers per task)\n- But catches issues early (cheaper than debugging compounded problems later)\n\n## Integration with Other Skills\n\n### With writing-plans\n\nThis skill EXECUTES plans created by the writing-plans skill:\n1. User requirements → writing-plans → implementation plan\n2. Implementation plan → subagent-driven-development → working code\n\n### With test-driven-development\n\nImplementer subagents should follow TDD:\n1. Write failing test first\n2. Implement minimal code\n3. Verify test passes\n4. Commit\n\nInclude TDD instructions in every implementer context.\n\n### With requesting-code-review\n\nThe two-stage review process IS the code review. For final integration review, use the requesting-code-review skill's review dimensions.\n\n### With systematic-debugging\n\nIf a subagent encounters bugs during implementation:\n1. Follow systematic-debugging process\n2. Find root cause before fixing\n3. Write regression test\n4. Resume implementation\n\n## Example Workflow\n\n```\n[Read plan: docs\u002Fplans\u002Fauth-feature.md]\n[Create todo list with 5 tasks]\n\n--- Task 1: Create User model ---\n[Dispatch implementer subagent]\n  Implementer: \"Should email be unique?\"\n  You: \"Yes, email must be unique\"\n  Implementer: Implemented, 3\u002F3 tests passing, committed.\n\n[Dispatch spec reviewer]\n  Spec reviewer: ✅ PASS — all requirements met\n\n[Dispatch quality reviewer]\n  Quality reviewer: ✅ APPROVED — clean code, good tests\n\n[Mark Task 1 complete]\n\n--- Task 2: Password hashing ---\n[Dispatch implementer subagent]\n  Implementer: No questions, implemented, 5\u002F5 tests passing.\n\n[Dispatch spec reviewer]\n  Spec reviewer: ❌ Missing: password strength validation (spec says \"min 8 chars\")\n\n[Implementer fixes]\n  Implementer: Added validation, 7\u002F7 tests passing.\n\n[Dispatch spec reviewer again]\n  Spec reviewer: ✅ PASS\n\n[Dispatch quality reviewer]\n  Quality reviewer: Important: Magic number 8, extract to constant\n  Implementer: Extracted MIN_PASSWORD_LENGTH constant\n  Quality reviewer: ✅ APPROVED\n\n[Mark Task 2 complete]\n\n... (continue for all tasks)\n\n[After all tasks: dispatch final integration reviewer]\n[Run full test suite: all passing]\n[Done!]\n```\n\n## Remember\n\n```\nFresh subagent per task\nTwo-stage review every time\nSpec compliance FIRST\nCode quality SECOND\nNever skip reviews\nCatch issues early\n```\n\n**Quality is not an accident. It's the result of systematic process.**\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"description":7},"Hermes Agent (adapted from obra\u002Fsuperpowers)","1.1.0",{"hermes":27},{"tags":28,"related_skills":34},[29,30,31,32,33],"delegation","subagent","implementation","workflow","parallel",[35,36,37],"writing-plans","requesting-code-review","test-driven-development","main","cef85894d3d9a4c9dabe5a90887d5ac59fe4ff0f","repos\u002Ftrident_hermes-agent_nousresearch_growing_ai\u002Fskills\u002Fsoftware-development\u002Fsubagent-driven-development","https:\u002F\u002Fgithub.com\u002Fmfrancime\u002Ftrident-archive","https:\u002F\u002Fgithub.com\u002Fmfrancime","2026-09-11 19:19:01",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add mfrancime\u002Ftrident-archive --skill subagent-driven-development",{"tool":50,"command":51},"bunx","bunx skills add mfrancime\u002Ftrident-archive --skill subagent-driven-development",{"tool":53,"command":54},"pnpm","pnpm dlx skills add mfrancime\u002Ftrident-archive --skill subagent-driven-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmfrancime\u002Ftrident-archive\u002Fblob\u002Fmain\u002Frepos\u002Ftrident_hermes-agent_nousresearch_growing_ai\u002Fskills\u002Fsoftware-development\u002Fsubagent-driven-development\u002FSKILL.md",true,[],[59,68,76,84,91,98],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":64,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M78VKWV0YXDY47JW2S4M19R1","skill-creator","Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmfrancime\u002Ftrident-archive\u002Fblob\u002Fmain\u002Frepos\u002Ftrident_orcaclaw_sakana_personal_ai_assistant\u002Fskills\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Fmfrancime\u002Ftrident-archive\u002Fblob\u002Fmain\u002Frepos\u002Ftrident_orcaclaw_sakana_personal_ai_assistant\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M78VGSK0VQR8DFB181VS4MN8","prose","OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.","https:\u002F\u002Fgithub.com\u002Fmfrancime\u002Ftrident-archive\u002Fblob\u002Fmain\u002Frepos\u002Ftrident_orcaclaw_sakana_personal_ai_assistant\u002Fextensions\u002Fopen-prose\u002Fskills\u002Fprose\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmfrancime\u002Ftrident-archive\u002Fblob\u002Fmain\u002Frepos\u002Ftrident_orcaclaw_sakana_personal_ai_assistant\u002Fextensions\u002Fopen-prose\u002Fskills\u002Fprose\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M78VFJ4N00J9RMF7X5AVZY7C","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fmfrancime\u002Ftrident-archive\u002Fblob\u002Fmain\u002Frepos\u002Ftrident_kilo-marketplace_skills_mcp_catalog\u002Fskills\u002Fwebapp-testing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmfrancime\u002Ftrident-archive\u002Fblob\u002Fmain\u002Frepos\u002Ftrident_kilo-marketplace_skills_mcp_catalog\u002Fskills\u002Fwebapp-testing\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":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M78VF9C8TQ37WGS6WBT77BVW","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Fmfrancime\u002Ftrident-archive\u002Fblob\u002Fmain\u002Frepos\u002Ftrident_kilo-marketplace_skills_mcp_catalog\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M78VF5VFD2CA77AM9AVBXR7C","vercel-deploy","Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as \"Deploy my app\", \"Deploy this to production\", \"Create a preview deployment\", \"Deploy and give me the link\", or \"Push this live\". No authentication required - returns preview URL and claimable deployment link.","https:\u002F\u002Fgithub.com\u002Fmfrancime\u002Ftrident-archive\u002Fblob\u002Fmain\u002Frepos\u002Ftrident_kilo-marketplace_skills_mcp_catalog\u002Fskills\u002Fvercel-deploy\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M78VF0JF37J4KCM4Y30Z9E55","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002Fmfrancime\u002Ftrident-archive\u002Fblob\u002Fmain\u002Frepos\u002Ftrident_kilo-marketplace_skills_mcp_catalog\u002Fskills\u002Fvercel-composition-patterns\u002FSKILL.md",[],[]]