[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79GJH54SNK8RY3BRWYR6FGE":3,"skill-same:01M79GJH54SNK8RY3BRWYR6FGE":43},{"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":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M79GJH54SNK8RY3BRWYR6FGE","spec-kit",null,"Spec-Driven Development (SDD) advisor using GitHub Spec Kit methodology. Kích hoạt skill này khi user muốn: (1) bắt đầu build feature\u002Fproject mới với AI coding agent, (2) tạo specification từ requirements, (3) tạo technical plan từ spec, (4) breakdown tasks từ plan, (5) hỏi về SDD workflow, slash commands speckit.*, specify CLI, hoặc bất kỳ câu hỏi nào liên quan đến Spec-Driven Development. Trigger aggressively cho: \"tạo spec\", \"viết spec\", \"SDD\", \"spec kit\", \"spec-driven\", \"speckit\", \"feature spec\", \"tạo feature mới\", \"plan feature\", \"breakdown tasks\", \"specify init\", \"speckit.specify\", \"speckit.plan\", \"speckit.tasks\", \"speckit.implement\".","luckyboy120794\u002FCowork_FAG3","luckyboy120794","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F58225127?v=4","01M79G5TSJYK6784KFN0JNN2FE","01M79G5TT5SWZW8YQR18V4GTS2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fluckyboy120794\u002FCowork_FAG3\u002Fblob\u002Ffor_merge\u002F.skills\u002Fspec-kit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: spec-kit\ndescription: >\n  Spec-Driven Development (SDD) advisor using GitHub Spec Kit methodology. Kích hoạt skill này\n  khi user muốn: (1) bắt đầu build feature\u002Fproject mới với AI coding agent, (2) tạo specification\n  từ requirements, (3) tạo technical plan từ spec, (4) breakdown tasks từ plan, (5) hỏi về SDD\n  workflow, slash commands speckit.*, specify CLI, hoặc bất kỳ câu hỏi nào liên quan đến\n  Spec-Driven Development. Trigger aggressively cho: \"tạo spec\", \"viết spec\", \"SDD\", \"spec kit\",\n  \"spec-driven\", \"speckit\", \"feature spec\", \"tạo feature mới\", \"plan feature\", \"breakdown tasks\",\n  \"specify init\", \"speckit.specify\", \"speckit.plan\", \"speckit.tasks\", \"speckit.implement\".\n---\n\n# Spec Kit — Spec-Driven Development Advisor\n\n## Core Philosophy\n\n**Spec-Driven Development (SDD)** flips traditional workflow:\n- ❌ Truyền thống: Code → (Spec là scaffolding bỏ đi)\n- ✅ SDD: **Spec → executable → Code** (Spec trở thành source of truth)\n\n**3 nguyên tắc:**\n1. **Intent-driven** — Spec định nghĩa *what* + *why*, không phải *how*\n2. **Multi-step refinement** — Không one-shot generation từ prompt\n3. **Heavy AI** — AI interpret spec, không phải viết code từ đầu\n\n---\n\n## Workflow Chuẩn (7 Bước)\n\n```\nSTEP 1: Constitution  →  project principles & guidelines\nSTEP 2: Specify       →  functional spec (what + why, NO tech stack)\nSTEP 3: Clarify       →  refine underspecified areas (BEFORE plan)\nSTEP 4: Plan          →  technical implementation plan (tech stack ở đây)\nSTEP 5: Validate      →  cross-check plan, remove over-engineering\nSTEP 6: Tasks         →  actionable task breakdown với dependencies\nSTEP 7: Implement     →  execute tasks theo order\n```\n\n---\n\n## Slash Commands Reference\n\n### Core Commands (bắt buộc)\n\n| Command | Mục đích |\n|---|---|\n| `\u002Fspeckit.constitution` | Tạo\u002Fupdate project governing principles |\n| `\u002Fspeckit.specify` | Mô tả feature cần build (what + why) |\n| `\u002Fspeckit.plan` | Tech stack + architecture choices |\n| `\u002Fspeckit.tasks` | Generate actionable task list |\n| `\u002Fspeckit.implement` | Execute tất cả tasks |\n| `\u002Fspeckit.converge` | Assess codebase vs spec → append remaining work |\n\n### Optional Commands (nâng cao)\n\n| Command | Mục đích |\n|---|---|\n| `\u002Fspeckit.clarify` | Hỏi về underspecified areas (chạy trước `\u002Fplan`) |\n| `\u002Fspeckit.analyze` | Cross-artifact consistency check (sau tasks, trước implement) |\n| `\u002Fspeckit.checklist` | Generate quality checklist — \"unit tests for English\" |\n| `\u002Fspeckit.taskstoissues` | Convert tasks → GitHub Issues |\n\n---\n\n## Setup\n\n### Cài đặt\n\n```bash\n# Requires Python 3.11+ và uv\nuv tool install specify-cli --from git+https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit.git@vX.Y.Z\n\n# Init project\nspecify init my-project --integration claude  # hoặc copilot, gemini, codex\n\n# Self-upgrade\nspecify self upgrade\nspecify self check  # kiểm tra version mới\n```\n\n### Supported Integrations\nClaude Code, GitHub Copilot, Gemini CLI, Codex CLI, Kiro CLI, và 25+ agents khác.\n\n---\n\n## Directory Structure Sau Khi Setup\n\n```\nproject\u002F\n├── CLAUDE.md (hoặc AGENTS.md)\n├── .specify\u002F\n│   ├── memory\u002F\n│   │   └── constitution.md          ← Project principles\n│   ├── scripts\u002Fbash\u002F                ← Automation scripts\n│   └── templates\u002F\n│       ├── spec-template.md\n│       ├── plan-template.md\n│       └── tasks-template.md\n└── specs\u002F\n    └── 001-feature-name\u002F\n        ├── spec.md                  ← Output of \u002Fspeckit.specify\n        ├── plan.md                  ← Output of \u002Fspeckit.plan\n        ├── tasks.md                 ← Output of \u002Fspeckit.tasks\n        ├── data-model.md\n        ├── research.md\n        └── contracts\u002F\n            └── api-spec.json\n```\n\n---\n\n## Hướng Dẫn Từng Bước\n\n### STEP 1 — Constitution\n```\n\u002Fspeckit.constitution Create principles focused on:\n- Code quality standards\n- Testing requirements (unit\u002Fintegration coverage %)\n- Performance targets\n- Security constraints\n- Naming conventions\n```\nOutput: `.specify\u002Fmemory\u002Fconstitution.md`\n\n---\n\n### STEP 2 — Specify (QUAN TRỌNG)\n> ⚠️ **Chỉ mô tả WHAT + WHY. Không đề cập tech stack.**\n\nPrompt tốt:\n```\n\u002Fspeckit.specify Build a [feature] that allows [who] to [do what].\nKey behaviors: [behavior 1], [behavior 2].\nConstraints: [no login required \u002F 5 predefined users \u002F etc].\n```\n\nPrompt xấu ❌:\n```\n\u002Fspeckit.specify Build a REST API with Spring Boot, MySQL, Redis cache...\n```\n\n---\n\n### STEP 3 — Clarify (bắt buộc trước Plan)\n```\n\u002Fspeckit.clarify\n```\n→ Agent hỏi structured questions về underspecified areas.\n→ Answers được ghi vào `spec.md` trong section Clarifications.\n\n---\n\n### STEP 4 — Plan (Tech Stack vào đây)\n```\n\u002Fspeckit.plan Use [tech stack]:\n- Backend: Spring Boot 3, PostgreSQL\n- Frontend: React + Vite\n- Auth: Keycloak\n```\nOutput: `plan.md`, `data-model.md`, `research.md`, `contracts\u002F`\n\n---\n\n### STEP 5 — Validate Plan\nPrompt gợi ý:\n```\nAudit the plan. Check:\n1. Anything missing or ambiguous?\n2. Any over-engineered components? Remove them.\n3. Does it follow constitution.md?\n4. Research rapidly-changing libs (spawn parallel tasks if needed).\n```\n\n---\n\n### STEP 6 — Tasks\n```\n\u002Fspeckit.tasks\n```\nOutput `tasks.md` chứa:\n- Tasks grouped by user story\n- `[P]` = parallel-safe tasks\n- Exact file paths\n- Dependencies\n- Checkpoint validations\n\n---\n\n### STEP 7 — Implement\n```\n\u002Fspeckit.implement\n```\nPrerequisites được validate tự động (constitution → spec → plan → tasks).\n\n---\n\n## Customization: Extensions vs Presets vs Bundles\n\n| Goal | Dùng |\n|---|---|\n| Thêm command\u002Fworkflow mới | **Extension** |\n| Customize format spec\u002Fplan\u002Ftasks | **Preset** |\n| Integrate external tool (Jira, Slack) | **Extension** |\n| Enforce org\u002Fregulatory standards | **Preset** |\n| Provision full role-based setup 1 lệnh | **Bundle** |\n\n```bash\n# Extension\nspecify extension search\nspecify extension add \u003Cname>\n\n# Preset\nspecify preset search\nspecify preset add \u003Cname>\n\n# Bundle\nspecify bundle search\nspecify bundle install \u003Cbundle-id>\nspecify bundle validate --path .\u002Fmy-bundle\nspecify bundle build --path .\u002Fmy-bundle\n```\n\n---\n\n## Development Phases\n\n| Phase | Khi nào dùng |\n|---|---|\n| **0-to-1 (Greenfield)** | Project mới từ đầu |\n| **Creative Exploration** | Explore parallel implementations |\n| **Iterative (Brownfield)** | Add feature vào project hiện tại |\n\n**Brownfield rule:** Giữ Spec Kit tooling updates tách biệt với feature artifact evolution.\n\n---\n\n## Anti-Patterns Cần Tránh\n\n1. ❌ Skip `\u002Fspeckit.clarify` → rework plan downstream\n2. ❌ Đưa tech stack vào `\u002Fspeckit.specify` → làm hỏng intent-driven approach\n3. ❌ Accept first attempt của agent → luôn iterate\n4. ❌ Over-engineering — agent có xu hướng thêm components không cần thiết → luôn audit\n5. ❌ One-shot generation từ 1 prompt dài → dùng multi-step workflow\n\n---\n\n## Quick Reference cho Android Automotive Projects\n\nKhi dùng Spec Kit cho AAOS\u002FIVI feature:\n\n**Constitution nên include:**\n- CarNotConnectedException handling pattern\n- Thread safety requirements (main thread vs binder thread)\n- `@GuardedBy` annotation enforcement\n- Null safety cho CarService callbacks\n- Timeout handling cho VHAL requests\n\n**Specify nên mô tả:**\n- Use case từ góc nhìn driver\u002Fpassenger\n- Safety constraints (ví dụ: không block UI thread)\n- CarUxRestrictions compliance\n\n**Plan nên specify:**\n- AAOS version (AAOS13 vs AAOS15)\n- CarService APIs cụ thể\n- AIDL interface design\n- Multi-user behavior\n","# Spec Kit — Spec-Driven Development Advisor\n\n## Core Philosophy\n\n**Spec-Driven Development (SDD)** flips traditional workflow:\n- ❌ Truyền thống: Code → (Spec là scaffolding bỏ đi)\n- ✅ SDD: **Spec → executable → Code** (Spec trở thành source of truth)\n\n**3 nguyên tắc:**\n1. **Intent-driven** — Spec định nghĩa *what* + *why*, không phải *how*\n2. **Multi-step refinement** — Không one-shot generation từ prompt\n3. **Heavy AI** — AI interpret spec, không phải viết code từ đầu\n\n---\n\n## Workflow Chuẩn (7 Bước)\n\n```\nSTEP 1: Constitution  →  project principles & guidelines\nSTEP 2: Specify       →  functional spec (what + why, NO tech stack)\nSTEP 3: Clarify       →  refine underspecified areas (BEFORE plan)\nSTEP 4: Plan          →  technical implementation plan (tech stack ở đây)\nSTEP 5: Validate      →  cross-check plan, remove over-engineering\nSTEP 6: Tasks         →  actionable task breakdown với dependencies\nSTEP 7: Implement     →  execute tasks theo order\n```\n\n---\n\n## Slash Commands Reference\n\n### Core Commands (bắt buộc)\n\n| Command | Mục đích |\n|---|---|\n| `\u002Fspeckit.constitution` | Tạo\u002Fupdate project governing principles |\n| `\u002Fspeckit.specify` | Mô tả feature cần build (what + why) |\n| `\u002Fspeckit.plan` | Tech stack + architecture choices |\n| `\u002Fspeckit.tasks` | Generate actionable task list |\n| `\u002Fspeckit.implement` | Execute tất cả tasks |\n| `\u002Fspeckit.converge` | Assess codebase vs spec → append remaining work |\n\n### Optional Commands (nâng cao)\n\n| Command | Mục đích |\n|---|---|\n| `\u002Fspeckit.clarify` | Hỏi về underspecified areas (chạy trước `\u002Fplan`) |\n| `\u002Fspeckit.analyze` | Cross-artifact consistency check (sau tasks, trước implement) |\n| `\u002Fspeckit.checklist` | Generate quality checklist — \"unit tests for English\" |\n| `\u002Fspeckit.taskstoissues` | Convert tasks → GitHub Issues |\n\n---\n\n## Setup\n\n### Cài đặt\n\n```bash\n# Requires Python 3.11+ và uv\nuv tool install specify-cli --from git+https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit.git@vX.Y.Z\n\n# Init project\nspecify init my-project --integration claude  # hoặc copilot, gemini, codex\n\n# Self-upgrade\nspecify self upgrade\nspecify self check  # kiểm tra version mới\n```\n\n### Supported Integrations\nClaude Code, GitHub Copilot, Gemini CLI, Codex CLI, Kiro CLI, và 25+ agents khác.\n\n---\n\n## Directory Structure Sau Khi Setup\n\n```\nproject\u002F\n├── CLAUDE.md (hoặc AGENTS.md)\n├── .specify\u002F\n│   ├── memory\u002F\n│   │   └── constitution.md          ← Project principles\n│   ├── scripts\u002Fbash\u002F                ← Automation scripts\n│   └── templates\u002F\n│       ├── spec-template.md\n│       ├── plan-template.md\n│       └── tasks-template.md\n└── specs\u002F\n    └── 001-feature-name\u002F\n        ├── spec.md                  ← Output of \u002Fspeckit.specify\n        ├── plan.md                  ← Output of \u002Fspeckit.plan\n        ├── tasks.md                 ← Output of \u002Fspeckit.tasks\n        ├── data-model.md\n        ├── research.md\n        └── contracts\u002F\n            └── api-spec.json\n```\n\n---\n\n## Hướng Dẫn Từng Bước\n\n### STEP 1 — Constitution\n```\n\u002Fspeckit.constitution Create principles focused on:\n- Code quality standards\n- Testing requirements (unit\u002Fintegration coverage %)\n- Performance targets\n- Security constraints\n- Naming conventions\n```\nOutput: `.specify\u002Fmemory\u002Fconstitution.md`\n\n---\n\n### STEP 2 — Specify (QUAN TRỌNG)\n> ⚠️ **Chỉ mô tả WHAT + WHY. Không đề cập tech stack.**\n\nPrompt tốt:\n```\n\u002Fspeckit.specify Build a [feature] that allows [who] to [do what].\nKey behaviors: [behavior 1], [behavior 2].\nConstraints: [no login required \u002F 5 predefined users \u002F etc].\n```\n\nPrompt xấu ❌:\n```\n\u002Fspeckit.specify Build a REST API with Spring Boot, MySQL, Redis cache...\n```\n\n---\n\n### STEP 3 — Clarify (bắt buộc trước Plan)\n```\n\u002Fspeckit.clarify\n```\n→ Agent hỏi structured questions về underspecified areas.\n→ Answers được ghi vào `spec.md` trong section Clarifications.\n\n---\n\n### STEP 4 — Plan (Tech Stack vào đây)\n```\n\u002Fspeckit.plan Use [tech stack]:\n- Backend: Spring Boot 3, PostgreSQL\n- Frontend: React + Vite\n- Auth: Keycloak\n```\nOutput: `plan.md`, `data-model.md`, `research.md`, `contracts\u002F`\n\n---\n\n### STEP 5 — Validate Plan\nPrompt gợi ý:\n```\nAudit the plan. Check:\n1. Anything missing or ambiguous?\n2. Any over-engineered components? Remove them.\n3. Does it follow constitution.md?\n4. Research rapidly-changing libs (spawn parallel tasks if needed).\n```\n\n---\n\n### STEP 6 — Tasks\n```\n\u002Fspeckit.tasks\n```\nOutput `tasks.md` chứa:\n- Tasks grouped by user story\n- `[P]` = parallel-safe tasks\n- Exact file paths\n- Dependencies\n- Checkpoint validations\n\n---\n\n### STEP 7 — Implement\n```\n\u002Fspeckit.implement\n```\nPrerequisites được validate tự động (constitution → spec → plan → tasks).\n\n---\n\n## Customization: Extensions vs Presets vs Bundles\n\n| Goal | Dùng |\n|---|---|\n| Thêm command\u002Fworkflow mới | **Extension** |\n| Customize format spec\u002Fplan\u002Ftasks | **Preset** |\n| Integrate external tool (Jira, Slack) | **Extension** |\n| Enforce org\u002Fregulatory standards | **Preset** |\n| Provision full role-based setup 1 lệnh | **Bundle** |\n\n```bash\n# Extension\nspecify extension search\nspecify extension add \u003Cname>\n\n# Preset\nspecify preset search\nspecify preset add \u003Cname>\n\n# Bundle\nspecify bundle search\nspecify bundle install \u003Cbundle-id>\nspecify bundle validate --path .\u002Fmy-bundle\nspecify bundle build --path .\u002Fmy-bundle\n```\n\n---\n\n## Development Phases\n\n| Phase | Khi nào dùng |\n|---|---|\n| **0-to-1 (Greenfield)** | Project mới từ đầu |\n| **Creative Exploration** | Explore parallel implementations |\n| **Iterative (Brownfield)** | Add feature vào project hiện tại |\n\n**Brownfield rule:** Giữ Spec Kit tooling updates tách biệt với feature artifact evolution.\n\n---\n\n## Anti-Patterns Cần Tránh\n\n1. ❌ Skip `\u002Fspeckit.clarify` → rework plan downstream\n2. ❌ Đưa tech stack vào `\u002Fspeckit.specify` → làm hỏng intent-driven approach\n3. ❌ Accept first attempt của agent → luôn iterate\n4. ❌ Over-engineering — agent có xu hướng thêm components không cần thiết → luôn audit\n5. ❌ One-shot generation từ 1 prompt dài → dùng multi-step workflow\n\n---\n\n## Quick Reference cho Android Automotive Projects\n\nKhi dùng Spec Kit cho AAOS\u002FIVI feature:\n\n**Constitution nên include:**\n- CarNotConnectedException handling pattern\n- Thread safety requirements (main thread vs binder thread)\n- `@GuardedBy` annotation enforcement\n- Null safety cho CarService callbacks\n- Timeout handling cho VHAL requests\n\n**Specify nên mô tả:**\n- Use case từ góc nhìn driver\u002Fpassenger\n- Safety constraints (ví dụ: không block UI thread)\n- CarUxRestrictions compliance\n\n**Plan nên specify:**\n- AAOS version (AAOS13 vs AAOS15)\n- CarService APIs cụ thể\n- AIDL interface design\n- Multi-user behavior\n",{"name":5,"description":7},"for_merge","c125351f10302e3a2dacbe0c1f56ab02e49f8d63",".skills\u002Fspec-kit","https:\u002F\u002Fgithub.com\u002Fluckyboy120794\u002FCowork_FAG3","https:\u002F\u002Fgithub.com\u002Fluckyboy120794","2026-07-21 16:59:00",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add luckyboy120794\u002FCowork_FAG3 --skill spec-kit",{"tool":35,"command":36},"bunx","bunx skills add luckyboy120794\u002FCowork_FAG3 --skill spec-kit",{"tool":38,"command":39},"pnpm","pnpm dlx skills add luckyboy120794\u002FCowork_FAG3 --skill spec-kit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fluckyboy120794\u002FCowork_FAG3\u002Fblob\u002Ffor_merge\u002F.skills\u002Fspec-kit\u002FSKILL.md",true,[],[44,51,58,65,72,79],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M79GN00AB2SSPMB8358HGYD8","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fluckyboy120794\u002FCowork_FAG3\u002Fblob\u002Ffor_merge\u002F.skills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M79GMXZ4CC9X207HDASJT023","writing-shape","Writing, exploit — shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Fluckyboy120794\u002FCowork_FAG3\u002Fblob\u002Ffor_merge\u002F.skills\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M79GMVHHJDFA5ZVGRJYYV4FW","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fluckyboy120794\u002FCowork_FAG3\u002Fblob\u002Ffor_merge\u002F.skills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M79GMSVVAMSY5R0Z2GJMG3AR","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002Fluckyboy120794\u002FCowork_FAG3\u002Fblob\u002Ffor_merge\u002F.skills\u002Fwriting-great-skills\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M79GMRDMD8G98ZWK11QW8J00","writing-fragments","Writing, explore — mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Fluckyboy120794\u002FCowork_FAG3\u002Fblob\u002Ffor_merge\u002F.skills\u002Fwriting-fragments\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M79GMPDD3BE81JVKV2E3WRPY","writing-beats","Writing, exploit — assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002Fluckyboy120794\u002FCowork_FAG3\u002Fblob\u002Ffor_merge\u002F.skills\u002Fwriting-beats\u002FSKILL.md",[],[]]