[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79XKYV704PA65KSNAMC2QZX":3,"skill-same:01M79XKYV704PA65KSNAMC2QZX":86},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M79XKYV704PA65KSNAMC2QZX","grill-with-docs",null,"Docs-anchored grilling session — challenges a plan against the project's existing language (CONTEXT.md) and recorded decisions (docs\u002Fadr\u002F), and updates those files inline as terminology and decisions crystallise. Use when user wants to stress-test a plan against documented domain language, or mentions \"grill with docs\".","Heverton-web\u002Fproj_livros","Heverton-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136394064?v=4","01M79STQDWSTA88J5CA9QR184V","Heverton Eduardo Peres","01M79STQEFTTYHD3AC7F2RRW5T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrill-with-docs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: grill-with-docs\ndescription: Docs-anchored grilling session — challenges a plan against the project's existing language (CONTEXT.md) and recorded decisions (docs\u002Fadr\u002F), and updates those files inline as terminology and decisions crystallise. Use when user wants to stress-test a plan against documented domain language, or mentions \"grill with docs\".\nlicense: MIT\nmetadata:\n  derived_from: \"https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Fengineering\u002Fgrill-with-docs\"\n  original_author: \"Matt Pocock (@mattpocock)\"\n  original_license: MIT\n  voice: \"Matt Pocock — relentless, one-at-a-time, codebase-and-docs-first, ADRs only when 3 criteria are met\"\n  version: 1.0.0\n---\n\n# Grill with Docs\n\n> Derived from [Matt Pocock's grill-with-docs](https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Fengineering\u002Fgrill-with-docs) (MIT, © 2026 Matt Pocock). Matt's interview discipline + docs-anchored grilling rules preserved verbatim under MIT. Additions in this repo: 3 stdlib validators (CONTEXT.md linter, ADR scanner, glossary↔code consistency check), 3 in-depth references each citing 7+ authoritative sources, `cs-grill-with-docs` agent, `\u002Fcs:grill-with-docs` command. See [Wrapper additions](#wrapper-additions) below.\n\n\u003Cwhat-to-do>\n\nInterview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.\n\nAsk the questions one at a time, waiting for feedback on each question before continuing.\n\nIf a question can be answered by exploring the codebase, explore the codebase instead.\n\n\u003C\u002Fwhat-to-do>\n\n\u003Csupporting-info>\n\n## Domain awareness\n\nDuring codebase exploration, also look for existing documentation:\n\n### File structure\n\nMost repos have a single context:\n\n```\n\u002F\n├── CONTEXT.md\n├── docs\u002F\n│   └── adr\u002F\n│       ├── 0001-event-sourced-orders.md\n│       └── 0002-postgres-for-write-model.md\n└── src\u002F\n```\n\nIf a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:\n\n```\n\u002F\n├── CONTEXT-MAP.md\n├── docs\u002F\n│   └── adr\u002F                          ← system-wide decisions\n├── src\u002F\n│   ├── ordering\u002F\n│   │   ├── CONTEXT.md\n│   │   └── docs\u002Fadr\u002F                 ← context-specific decisions\n│   └── billing\u002F\n│       ├── CONTEXT.md\n│       └── docs\u002Fadr\u002F\n```\n\nCreate files lazily — only when you have something to write. If no `CONTEXT.md` exists, create one when the first term is resolved. If no `docs\u002Fadr\u002F` exists, create it when the first ADR is needed.\n\n## During the session\n\n### Challenge against the glossary\n\nWhen the user uses a term that conflicts with the existing language in `CONTEXT.md`, call it out immediately. \"Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?\"\n\n### Sharpen fuzzy language\n\nWhen the user uses vague or overloaded terms, propose a precise canonical term. \"You're saying 'account' — do you mean the Customer or the User? Those are different things.\"\n\n### Discuss concrete scenarios\n\nWhen domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.\n\n### Cross-reference with code\n\nWhen the user states how something works, check whether the code agrees. If you find a contradiction, surface it: \"Your code cancels entire Orders, but you just said partial cancellation is possible — which is right?\"\n\n### Update CONTEXT.md inline\n\nWhen a term is resolved, update `CONTEXT.md` right there. Don't batch these up — capture them as they happen. Use the format in [CONTEXT-FORMAT.md](.\u002FCONTEXT-FORMAT.md).\n\n`CONTEXT.md` should be totally devoid of implementation details. Do not treat `CONTEXT.md` as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.\n\n### Offer ADRs sparingly\n\nOnly offer to create an ADR when all three are true:\n\n1. **Hard to reverse** — the cost of changing your mind later is meaningful\n2. **Surprising without context** — a future reader will wonder \"why did they do it this way?\"\n3. **The result of a real trade-off** — there were genuine alternatives and you picked one for specific reasons\n\nIf any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](.\u002FADR-FORMAT.md).\n\n\u003C\u002Fsupporting-info>\n\n## Wrapper Additions\n\nThe additions below are **not** part of Matt's upstream skill. They operationalize the upstream's rules into deterministic, stdlib-only validators that pair naturally with the interview loop.\n\n### Workflow (with wrapper tools)\n\n1. **Pre-flight (before the first question):**\n   - Run `scripts\u002Fcontext_md_linter.py CONTEXT.md` if a `CONTEXT.md` exists — confirms the glossary is well-formed before grilling against it.\n   - Run `scripts\u002Fadr_scanner.py docs\u002Fadr\u002F` if `docs\u002Fadr\u002F` exists — surfaces numbering gaps, malformed ADRs, status-frontmatter inconsistencies.\n   - Run `scripts\u002Fglossary_code_consistency.py --context CONTEXT.md --code src\u002F` — flags defined-but-unused terms (dead glossary) and code-only common nouns that may need definitions. Use these flags as opening grill questions.\n\n2. **During the session (Matt's rules apply):**\n   - One question per turn, walking depth-first.\n   - When a term is sharpened: edit `CONTEXT.md` immediately; re-run `context_md_linter.py` if the edit is structural.\n   - When an ADR is warranted: write it under `docs\u002Fadr\u002F`; re-run `adr_scanner.py` to confirm numbering.\n\n3. **Closing:**\n   - Final `glossary_code_consistency.py` run to confirm no new orphan terms were introduced.\n   - Summarize: terms added\u002Frefined, ADRs written, scenarios discussed, open items.\n\n### Tools (stdlib-only)\n\n| Tool | One-line role |\n|---|---|\n| `scripts\u002Fcontext_md_linter.py` | Validate `CONTEXT.md` against the CONTEXT-FORMAT.md structure. PASS\u002FWARN\u002FFAIL per rule. |\n| `scripts\u002Fadr_scanner.py` | Walk `docs\u002Fadr\u002F`, check `NNNN-slug.md` pattern, numbering integrity, body completeness. |\n| `scripts\u002Fglossary_code_consistency.py` | Cross-reference bold terms in `CONTEXT.md` against codebase usage. Flag dead glossary + code-only common nouns. |\n\n### References (citations behind each rule)\n\n- [`references\u002Fubiquitous_language.md`](references\u002Fubiquitous_language.md) — why a glossary belongs in source control (Evans, Vernon, Khononov, Wlaschin, Brandolini, Avram & Marinescu, Fowler)\n- [`references\u002Fadr_practice.md`](references\u002Fadr_practice.md) — when an ADR earns its keep (Nygard, Tyree & Akerman, Zimmermann Y-statements, MADR, ThoughtWorks Radar, adr-tools, Backstage)\n- [`references\u002Fcontext_md_as_artifact.md`](references\u002Fcontext_md_as_artifact.md) — CONTEXT.md as living artifact (Khononov on language drift, Kernighan on naming, BoundedContext bliki, Confluent on data contracts, Brandolini on EventStorming glossary)\n\n### Companion\n\n- Agent: `cs-grill-with-docs` (see `..\u002F..\u002Fagents\u002Fcs-grill-with-docs.md`)\n- Command: `\u002Fcs:grill-with-docs` (see `..\u002F..\u002Fcommands\u002Fcs-grill-with-docs.md`)\n\n---\n\n**Version:** 1.0.0\n**Derived:** Matt Pocock's grill-with-docs (MIT) + this repo's wrapper\n","# Grill with Docs\n\n> Derived from [Matt Pocock's grill-with-docs](https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Fengineering\u002Fgrill-with-docs) (MIT, © 2026 Matt Pocock). Matt's interview discipline + docs-anchored grilling rules preserved verbatim under MIT. Additions in this repo: 3 stdlib validators (CONTEXT.md linter, ADR scanner, glossary↔code consistency check), 3 in-depth references each citing 7+ authoritative sources, `cs-grill-with-docs` agent, `\u002Fcs:grill-with-docs` command. See [Wrapper additions](#wrapper-additions) below.\n\n\u003Cwhat-to-do>\n\nInterview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.\n\nAsk the questions one at a time, waiting for feedback on each question before continuing.\n\nIf a question can be answered by exploring the codebase, explore the codebase instead.\n\n\u003C\u002Fwhat-to-do>\n\n\u003Csupporting-info>\n\n## Domain awareness\n\nDuring codebase exploration, also look for existing documentation:\n\n### File structure\n\nMost repos have a single context:\n\n```\n\u002F\n├── CONTEXT.md\n├── docs\u002F\n│   └── adr\u002F\n│       ├── 0001-event-sourced-orders.md\n│       └── 0002-postgres-for-write-model.md\n└── src\u002F\n```\n\nIf a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:\n\n```\n\u002F\n├── CONTEXT-MAP.md\n├── docs\u002F\n│   └── adr\u002F                          ← system-wide decisions\n├── src\u002F\n│   ├── ordering\u002F\n│   │   ├── CONTEXT.md\n│   │   └── docs\u002Fadr\u002F                 ← context-specific decisions\n│   └── billing\u002F\n│       ├── CONTEXT.md\n│       └── docs\u002Fadr\u002F\n```\n\nCreate files lazily — only when you have something to write. If no `CONTEXT.md` exists, create one when the first term is resolved. If no `docs\u002Fadr\u002F` exists, create it when the first ADR is needed.\n\n## During the session\n\n### Challenge against the glossary\n\nWhen the user uses a term that conflicts with the existing language in `CONTEXT.md`, call it out immediately. \"Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?\"\n\n### Sharpen fuzzy language\n\nWhen the user uses vague or overloaded terms, propose a precise canonical term. \"You're saying 'account' — do you mean the Customer or the User? Those are different things.\"\n\n### Discuss concrete scenarios\n\nWhen domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.\n\n### Cross-reference with code\n\nWhen the user states how something works, check whether the code agrees. If you find a contradiction, surface it: \"Your code cancels entire Orders, but you just said partial cancellation is possible — which is right?\"\n\n### Update CONTEXT.md inline\n\nWhen a term is resolved, update `CONTEXT.md` right there. Don't batch these up — capture them as they happen. Use the format in [CONTEXT-FORMAT.md](.\u002FCONTEXT-FORMAT.md).\n\n`CONTEXT.md` should be totally devoid of implementation details. Do not treat `CONTEXT.md` as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.\n\n### Offer ADRs sparingly\n\nOnly offer to create an ADR when all three are true:\n\n1. **Hard to reverse** — the cost of changing your mind later is meaningful\n2. **Surprising without context** — a future reader will wonder \"why did they do it this way?\"\n3. **The result of a real trade-off** — there were genuine alternatives and you picked one for specific reasons\n\nIf any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](.\u002FADR-FORMAT.md).\n\n\u003C\u002Fsupporting-info>\n\n## Wrapper Additions\n\nThe additions below are **not** part of Matt's upstream skill. They operationalize the upstream's rules into deterministic, stdlib-only validators that pair naturally with the interview loop.\n\n### Workflow (with wrapper tools)\n\n1. **Pre-flight (before the first question):**\n   - Run `scripts\u002Fcontext_md_linter.py CONTEXT.md` if a `CONTEXT.md` exists — confirms the glossary is well-formed before grilling against it.\n   - Run `scripts\u002Fadr_scanner.py docs\u002Fadr\u002F` if `docs\u002Fadr\u002F` exists — surfaces numbering gaps, malformed ADRs, status-frontmatter inconsistencies.\n   - Run `scripts\u002Fglossary_code_consistency.py --context CONTEXT.md --code src\u002F` — flags defined-but-unused terms (dead glossary) and code-only common nouns that may need definitions. Use these flags as opening grill questions.\n\n2. **During the session (Matt's rules apply):**\n   - One question per turn, walking depth-first.\n   - When a term is sharpened: edit `CONTEXT.md` immediately; re-run `context_md_linter.py` if the edit is structural.\n   - When an ADR is warranted: write it under `docs\u002Fadr\u002F`; re-run `adr_scanner.py` to confirm numbering.\n\n3. **Closing:**\n   - Final `glossary_code_consistency.py` run to confirm no new orphan terms were introduced.\n   - Summarize: terms added\u002Frefined, ADRs written, scenarios discussed, open items.\n\n### Tools (stdlib-only)\n\n| Tool | One-line role |\n|---|---|\n| `scripts\u002Fcontext_md_linter.py` | Validate `CONTEXT.md` against the CONTEXT-FORMAT.md structure. PASS\u002FWARN\u002FFAIL per rule. |\n| `scripts\u002Fadr_scanner.py` | Walk `docs\u002Fadr\u002F`, check `NNNN-slug.md` pattern, numbering integrity, body completeness. |\n| `scripts\u002Fglossary_code_consistency.py` | Cross-reference bold terms in `CONTEXT.md` against codebase usage. Flag dead glossary + code-only common nouns. |\n\n### References (citations behind each rule)\n\n- [`references\u002Fubiquitous_language.md`](references\u002Fubiquitous_language.md) — why a glossary belongs in source control (Evans, Vernon, Khononov, Wlaschin, Brandolini, Avram & Marinescu, Fowler)\n- [`references\u002Fadr_practice.md`](references\u002Fadr_practice.md) — when an ADR earns its keep (Nygard, Tyree & Akerman, Zimmermann Y-statements, MADR, ThoughtWorks Radar, adr-tools, Backstage)\n- [`references\u002Fcontext_md_as_artifact.md`](references\u002Fcontext_md_as_artifact.md) — CONTEXT.md as living artifact (Khononov on language drift, Kernighan on naming, BoundedContext bliki, Confluent on data contracts, Brandolini on EventStorming glossary)\n\n### Companion\n\n- Agent: `cs-grill-with-docs` (see `..\u002F..\u002Fagents\u002Fcs-grill-with-docs.md`)\n- Command: `\u002Fcs:grill-with-docs` (see `..\u002F..\u002Fcommands\u002Fcs-grill-with-docs.md`)\n\n---\n\n**Version:** 1.0.0\n**Derived:** Matt Pocock's grill-with-docs (MIT) + this repo's wrapper\n",{"name":5,"license":15,"metadata":24,"description":7},{"voice":25,"version":26,"derived_from":27,"original_author":28,"original_license":15},"Matt Pocock — relentless, one-at-a-time, codebase-and-docs-first, ADRs only when 3 criteria are met","1.0.0","https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Fengineering\u002Fgrill-with-docs","Matt Pocock (@mattpocock)","main","5eac686c0e84af1a5dc958c1bfb6c9d00699561d",".claude\u002Fskills\u002Fgrill-with-docs",1,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros","https:\u002F\u002Fgithub.com\u002FHeverton-web","2026-07-29 06:58:59",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Heverton-web\u002Fproj_livros --skill grill-with-docs",{"tool":42,"command":43},"bunx","bunx skills add Heverton-web\u002Fproj_livros --skill grill-with-docs",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Heverton-web\u002Fproj_livros --skill grill-with-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrill-with-docs\u002FSKILL.md",true,[50,56,60,64,68,72,78,82],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"ADR-FORMAT.md","REFERENCE","参考文档",2980,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrill-with-docs\u002FADR-FORMAT.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"CONTEXT-FORMAT.md",3363,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrill-with-docs\u002FCONTEXT-FORMAT.md",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fadr_practice.md",8742,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrill-with-docs\u002Freferences\u002Fadr_practice.md",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fcontext_md_as_artifact.md",9376,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrill-with-docs\u002Freferences\u002Fcontext_md_as_artifact.md",{"path":69,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fubiquitous_language.md",6849,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrill-with-docs\u002Freferences\u002Fubiquitous_language.md",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Fadr_scanner.py","SCRIPT","脚本",9667,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrill-with-docs\u002Fscripts\u002Fadr_scanner.py",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"scripts\u002Fcontext_md_linter.py",9943,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrill-with-docs\u002Fscripts\u002Fcontext_md_linter.py",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002Fglossary_code_consistency.py",10391,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrill-with-docs\u002Fscripts\u002Fglossary_code_consistency.py",[87,94,101,108,115,122],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7A3PZFSZ0K95BAD6QHJPX97","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002Fagentic\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7A3PH26QVPYRTM6EWS45YET","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002Fagentic\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7A3NVTC4N3NG1TA2SGSFGF6","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002Fagentic\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7A3NQNAJPSQ24VWSQ679AX8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002Fagentic\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7A3NE3FGSMGDY5XVKJ8297H","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002Fagentic\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M7A3N4ZG6TVJ1TST9C0T5QAK","webinar-marketing","When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar\u002Fevent motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002Fagentic\u002Fskills\u002Fwebinar-marketing\u002FSKILL.md",[],[]]