[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79YJCMVG9PSERQZWJC2S009":3,"skill-same:01M79YJCMVG9PSERQZWJC2S009":78},{"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},"01M79YJCMVG9PSERQZWJC2S009","seo-audit",null,"When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions \"SEO audit,\" \"technical SEO,\" \"why am I not ranking,\" \"SEO issues,\" \"on-page SEO,\" \"meta tags review,\" or \"SEO health check.\" For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.","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\u002Fseo-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"seo-audit\"\ndescription: When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions \"SEO audit,\" \"technical SEO,\" \"why am I not ranking,\" \"SEO issues,\" \"on-page SEO,\" \"meta tags review,\" or \"SEO health check.\" For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# SEO Audit\n\nYou are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore auditing, understand:\n\n1. **Site Context**\n   - What type of site? (SaaS, e-commerce, blog, etc.)\n   - What's the primary business goal for SEO?\n   - What keywords\u002Ftopics are priorities?\n\n2. **Current State**\n   - Any known issues or concerns?\n   - Current organic traffic level?\n   - Recent changes or migrations?\n\n3. **Scope**\n   - Full site audit or specific pages?\n   - Technical + on-page, or one focus area?\n   - Access to Search Console \u002F analytics?\n\n---\n\n## Audit Framework\n\nThe audit walks three layers — technical (crawl\u002Findexation\u002Fspeed), on-page (titles, headings, internal links, keyword targeting), content (intent match, E-E-A-T, thin\u002Fduplicate pages). Full framework: references\u002Fseo-audit-reference.md.\n\n**Core Web Vitals pass\u002Ffail thresholds** (75th percentile of real-user data; full triage in references\u002Fcwv-thresholds.md):\n\n| Metric | Good | Needs improvement | Poor |\n|---|---|---|---|\n| LCP (Largest Contentful Paint) | ≤ 2.5s | 2.5-4.0s | > 4.0s |\n| INP (Interaction to Next Paint) | ≤ 200ms | 200-500ms | > 500ms |\n| CLS (Cumulative Layout Shift) | ≤ 0.1 | 0.1-0.25 | > 0.25 |\n\n## Tools\n\n| Tool | Invocation | Output |\n|---|---|---|\n| On-page checker | `python3 scripts\u002Fseo_checker.py --file page.html` (or `--url https:\u002F\u002F...`; `--json`) | Scores a single page 0-100: title\u002Fmeta\u002Fheadings\u002Flinks\u002Fimages |\n| Health scorer | `python3 scripts\u002Fseo_health_scorer.py --checks checks.json --industry saas` (no arg = `--demo`; industries: saas\u002Fecommerce\u002Flocal\u002Fpublisher; `--json`) | Weighted 0-100 site health score across 7 categories |\n\nRun `seo_checker.py` on the key templates\u002Fpages during the on-page layer, and `seo_health_scorer.py` on the completed check matrix to produce the audit's headline score.\n\n## Output Format\n\n### Audit Report Structure\n\n**Executive Summary**\n- Overall health assessment — lead with the `seo_health_scorer.py` score and its weakest categories\n- Top 3-5 priority issues\n- Quick wins identified\n\n**Technical SEO Findings**\nFor each issue:\n- **Issue**: What's wrong\n- **Impact**: SEO impact (High\u002FMedium\u002FLow)\n- **Evidence**: How you found it\n- **Fix**: Specific recommendation\n- **Priority**: 1-5 or High\u002FMedium\u002FLow\n\n**On-Page SEO Findings**\nSame format as above\n\n**Content Findings**\nSame format as above\n\n**Prioritized Action Plan**\n1. Critical fixes (blocking indexation\u002Franking)\n2. High-impact improvements\n3. Quick wins (easy, immediate benefit)\n4. Long-term recommendations\n\n---\n\n## References\n\n- [SEO Audit Reference](references\u002Fseo-audit-reference.md): Full audit framework, scoring, and remediation patterns\n- [Core Web Vitals Thresholds](references\u002Fcwv-thresholds.md): LCP\u002FINP\u002FCLS targets and triage rules\n- [E-E-A-T Framework](references\u002Feeat-framework.md): Experience, Expertise, Authoritativeness, Trustworthiness checklist\n- [Schema Types](references\u002Fschema-types.md): Structured data patterns by content type\n\n---\n\n## Tools Referenced\n\n**Free Tools**\n- Google Search Console (essential)\n- Google PageSpeed Insights\n- Bing Webmaster Tools\n- Rich Results Test\n- Mobile-Friendly Test\n- Schema Validator\n\n**Paid Tools** (if available)\n- Screaming Frog\n- Ahrefs \u002F Semrush\n- Sitebulb\n- ContentKing\n\n---\n\n## Task-Specific Questions\n\n1. What pages\u002Fkeywords matter most?\n2. Do you have Search Console access?\n3. Any recent changes or migrations?\n4. Who are your top organic competitors?\n5. What's your current organic traffic baseline?\n\n---\n\n## Related Skills\n\n- **programmatic-seo** — WHEN: user wants to build SEO pages at scale after the audit identifies keyword gaps. WHEN NOT: don't use for diagnosing existing issues; stay in seo-audit mode.\n- **aeo** — WHEN: user wants to optimize for AI answer engines (SGE, Perplexity, ChatGPT) in addition to traditional search. WHEN NOT: don't use for purely technical crawl\u002Findexation issues.\n- **schema-markup** — WHEN: audit reveals missing structured data opportunities (FAQ, HowTo, Product, Review schemas). WHEN NOT: don't use as a standalone fix when core technical SEO is broken.\n- **site-architecture** — WHEN: audit uncovers poor internal linking, orphan pages, or crawl depth issues that need a structural redesign. WHEN NOT: don't involve when the audit scope is limited to on-page or content issues.\n- **content-strategy** — WHEN: audit reveals thin content, keyword gaps, or lack of topical authority requiring a content plan. WHEN NOT: don't use when the problem is purely technical (robots.txt, redirects, speed).\n- **marketing-context** — WHEN: always read first if `.claude\u002Fproduct-marketing-context.md` exists to avoid redundant questions. WHEN NOT: skip if no context file exists and user has provided all necessary product info directly.\n\n---\n\n## Communication\n\nAll audit output follows the **SEO Audit Quality Standard**:\n- Lead with the executive summary (3-5 bullets max)\n- Findings use the Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority format consistently\n- Prioritized Action Plan is always the final deliverable section\n- Avoid jargon without explanation; write for a technically-aware but non-SEO-specialist reader\n- Quick wins are called out explicitly and kept separate from high-effort recommendations\n- Never present recommendations without evidence or rationale\n\n---\n\n## Proactive Triggers\n\nAutomatically surface seo-audit recommendations when:\n\n1. **Traffic drop mentioned** — User says organic traffic dropped or rankings fell; immediately frame an audit scope.\n2. **Site migration or redesign** — User mentions a planned or recent URL change, platform switch, or redesign; flag pre\u002Fpost-migration audit needs.\n3. **\"Why isn't my page ranking?\"** — Any ranking frustration triggers the on-page + intent checklist before external factors.\n4. **Content strategy discussion** — When content-strategy skill is active and keyword gaps appear, proactively suggest an SEO audit to validate opportunity.\n5. **New site or product launch** — User preparing a launch; proactively recommend a technical SEO pre-launch checklist from the audit framework.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Executive Summary | Markdown bullets | 3-5 top issues + quick wins, suitable for sharing with stakeholders |\n| Technical SEO Findings | Structured table | Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority per finding |\n| On-Page SEO Findings | Structured table | Same format, focused on content and metadata |\n| Prioritized Action Plan | Numbered list | Ordered by impact × effort, grouped into Critical \u002F High \u002F Quick Wins |\n| Keyword Cannibalization Map | Table | Pages competing for same keyword with recommended canonical or redirect actions |\n","# SEO Audit\n\nYou are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore auditing, understand:\n\n1. **Site Context**\n   - What type of site? (SaaS, e-commerce, blog, etc.)\n   - What's the primary business goal for SEO?\n   - What keywords\u002Ftopics are priorities?\n\n2. **Current State**\n   - Any known issues or concerns?\n   - Current organic traffic level?\n   - Recent changes or migrations?\n\n3. **Scope**\n   - Full site audit or specific pages?\n   - Technical + on-page, or one focus area?\n   - Access to Search Console \u002F analytics?\n\n---\n\n## Audit Framework\n\nThe audit walks three layers — technical (crawl\u002Findexation\u002Fspeed), on-page (titles, headings, internal links, keyword targeting), content (intent match, E-E-A-T, thin\u002Fduplicate pages). Full framework: references\u002Fseo-audit-reference.md.\n\n**Core Web Vitals pass\u002Ffail thresholds** (75th percentile of real-user data; full triage in references\u002Fcwv-thresholds.md):\n\n| Metric | Good | Needs improvement | Poor |\n|---|---|---|---|\n| LCP (Largest Contentful Paint) | ≤ 2.5s | 2.5-4.0s | > 4.0s |\n| INP (Interaction to Next Paint) | ≤ 200ms | 200-500ms | > 500ms |\n| CLS (Cumulative Layout Shift) | ≤ 0.1 | 0.1-0.25 | > 0.25 |\n\n## Tools\n\n| Tool | Invocation | Output |\n|---|---|---|\n| On-page checker | `python3 scripts\u002Fseo_checker.py --file page.html` (or `--url https:\u002F\u002F...`; `--json`) | Scores a single page 0-100: title\u002Fmeta\u002Fheadings\u002Flinks\u002Fimages |\n| Health scorer | `python3 scripts\u002Fseo_health_scorer.py --checks checks.json --industry saas` (no arg = `--demo`; industries: saas\u002Fecommerce\u002Flocal\u002Fpublisher; `--json`) | Weighted 0-100 site health score across 7 categories |\n\nRun `seo_checker.py` on the key templates\u002Fpages during the on-page layer, and `seo_health_scorer.py` on the completed check matrix to produce the audit's headline score.\n\n## Output Format\n\n### Audit Report Structure\n\n**Executive Summary**\n- Overall health assessment — lead with the `seo_health_scorer.py` score and its weakest categories\n- Top 3-5 priority issues\n- Quick wins identified\n\n**Technical SEO Findings**\nFor each issue:\n- **Issue**: What's wrong\n- **Impact**: SEO impact (High\u002FMedium\u002FLow)\n- **Evidence**: How you found it\n- **Fix**: Specific recommendation\n- **Priority**: 1-5 or High\u002FMedium\u002FLow\n\n**On-Page SEO Findings**\nSame format as above\n\n**Content Findings**\nSame format as above\n\n**Prioritized Action Plan**\n1. Critical fixes (blocking indexation\u002Franking)\n2. High-impact improvements\n3. Quick wins (easy, immediate benefit)\n4. Long-term recommendations\n\n---\n\n## References\n\n- [SEO Audit Reference](references\u002Fseo-audit-reference.md): Full audit framework, scoring, and remediation patterns\n- [Core Web Vitals Thresholds](references\u002Fcwv-thresholds.md): LCP\u002FINP\u002FCLS targets and triage rules\n- [E-E-A-T Framework](references\u002Feeat-framework.md): Experience, Expertise, Authoritativeness, Trustworthiness checklist\n- [Schema Types](references\u002Fschema-types.md): Structured data patterns by content type\n\n---\n\n## Tools Referenced\n\n**Free Tools**\n- Google Search Console (essential)\n- Google PageSpeed Insights\n- Bing Webmaster Tools\n- Rich Results Test\n- Mobile-Friendly Test\n- Schema Validator\n\n**Paid Tools** (if available)\n- Screaming Frog\n- Ahrefs \u002F Semrush\n- Sitebulb\n- ContentKing\n\n---\n\n## Task-Specific Questions\n\n1. What pages\u002Fkeywords matter most?\n2. Do you have Search Console access?\n3. Any recent changes or migrations?\n4. Who are your top organic competitors?\n5. What's your current organic traffic baseline?\n\n---\n\n## Related Skills\n\n- **programmatic-seo** — WHEN: user wants to build SEO pages at scale after the audit identifies keyword gaps. WHEN NOT: don't use for diagnosing existing issues; stay in seo-audit mode.\n- **aeo** — WHEN: user wants to optimize for AI answer engines (SGE, Perplexity, ChatGPT) in addition to traditional search. WHEN NOT: don't use for purely technical crawl\u002Findexation issues.\n- **schema-markup** — WHEN: audit reveals missing structured data opportunities (FAQ, HowTo, Product, Review schemas). WHEN NOT: don't use as a standalone fix when core technical SEO is broken.\n- **site-architecture** — WHEN: audit uncovers poor internal linking, orphan pages, or crawl depth issues that need a structural redesign. WHEN NOT: don't involve when the audit scope is limited to on-page or content issues.\n- **content-strategy** — WHEN: audit reveals thin content, keyword gaps, or lack of topical authority requiring a content plan. WHEN NOT: don't use when the problem is purely technical (robots.txt, redirects, speed).\n- **marketing-context** — WHEN: always read first if `.claude\u002Fproduct-marketing-context.md` exists to avoid redundant questions. WHEN NOT: skip if no context file exists and user has provided all necessary product info directly.\n\n---\n\n## Communication\n\nAll audit output follows the **SEO Audit Quality Standard**:\n- Lead with the executive summary (3-5 bullets max)\n- Findings use the Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority format consistently\n- Prioritized Action Plan is always the final deliverable section\n- Avoid jargon without explanation; write for a technically-aware but non-SEO-specialist reader\n- Quick wins are called out explicitly and kept separate from high-effort recommendations\n- Never present recommendations without evidence or rationale\n\n---\n\n## Proactive Triggers\n\nAutomatically surface seo-audit recommendations when:\n\n1. **Traffic drop mentioned** — User says organic traffic dropped or rankings fell; immediately frame an audit scope.\n2. **Site migration or redesign** — User mentions a planned or recent URL change, platform switch, or redesign; flag pre\u002Fpost-migration audit needs.\n3. **\"Why isn't my page ranking?\"** — Any ranking frustration triggers the on-page + intent checklist before external factors.\n4. **Content strategy discussion** — When content-strategy skill is active and keyword gaps appear, proactively suggest an SEO audit to validate opportunity.\n5. **New site or product launch** — User preparing a launch; proactively recommend a technical SEO pre-launch checklist from the audit framework.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Executive Summary | Markdown bullets | 3-5 top issues + quick wins, suitable for sharing with stakeholders |\n| Technical SEO Findings | Structured table | Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority per finding |\n| On-Page SEO Findings | Structured table | Same format, focused on content and metadata |\n| Prioritized Action Plan | Numbered list | Ordered by impact × effort, grouped into Critical \u002F High \u002F Quick Wins |\n| Keyword Cannibalization Map | Table | Pages competing for same keyword with recommended canonical or redirect actions |\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"updated":26,"version":27,"category":28},"Alireza Rezvani",1772755200000,"1.0.0","marketing","main","5eac686c0e84af1a5dc958c1bfb6c9d00699561d",".claude\u002Fskills\u002Fseo-audit",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 seo-audit",{"tool":42,"command":43},"bunx","bunx skills add Heverton-web\u002Fproj_livros --skill seo-audit",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Heverton-web\u002Fproj_livros --skill seo-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-audit\u002FSKILL.md",true,[50,56,60,64,68,74],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcwv-thresholds.md","REFERENCE","参考文档",1751,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-audit\u002Freferences\u002Fcwv-thresholds.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Feeat-framework.md",2884,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-audit\u002Freferences\u002Feeat-framework.md",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fschema-types.md",2573,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-audit\u002Freferences\u002Fschema-types.md",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fseo-audit-reference.md",5987,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-audit\u002Freferences\u002Fseo-audit-reference.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Fseo_checker.py","SCRIPT","脚本",13415,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-audit\u002Fscripts\u002Fseo_checker.py",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Fseo_health_scorer.py",11345,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-audit\u002Fscripts\u002Fseo_health_scorer.py",[79,86,93,100,107,114],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"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",[],[]]