[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NH1RR025CDFK10YA9FT57":3,"skill-same:01M71NH1RR025CDFK10YA9FT57":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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":63},"01M71NH1RR025CDFK10YA9FT57","ln-912-community-announcer",null,"Composes and publishes announcements to GitHub Discussions. Use when sharing releases, updates, or news with the community.","vitalikpestov\u002FSkills-Catalog","vitalikpestov","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F13882997?v=4","01M71N4QG0CWRXX4R24JQZXDDQ","Vitalik Pestov","01M71N4QGMSYRW607DDSE0CQMM",2,"MIT","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fcommunity-engagement\u002Fskills\u002Fln-912-community-announcer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"announcer","ln","ln 912 community announcer","community","grep","read","sharing","webfetch","releases","github","news","with","Bash","updates","when","use","true","2026-11-10 10:56:23",false,"---\nname: ln-912-community-announcer\ndescription: \"Composes and publishes announcements to GitHub Discussions. Use when sharing releases, updates, or news with the community.\"\ndisable-model-invocation: true\nlicense: MIT\nallowed-tools: Read, Grep, Glob, Bash, WebFetch\n---\n\n> **Paths:** File paths (`references\u002F`, `..\u002Fln-*`) are relative to this skill directory.\n\n# ln-912-community-announcer\n\n**Type:** L3 Worker (standalone)\n**Category:** 9XX Community Engagement\nComposes and publishes structured announcements to GitHub Discussions (Announcements category).\n\n---\n\n## Phase 0: GitHub Discovery\n\n**MANDATORY READ:** Load `references\u002Fcommunity_github_discovery.md`\n\nExecute the discovery protocol. Extract:\n- `{owner}\u002F{repo}` for URLs and git commands\n- `repo.id` for GraphQL mutation\n- `categories[\"Announcements\"]` category ID for publishing\n- Verify Announcements category exists\n\nLoad strategy: check `docs\u002Fcommunity_engagement_strategy.md` in target project, fallback to `references\u002Fcommunity_strategy_template.md`. Extract Section 2 (Announcement Triggers) and Section 6 (Tone Guide).\n\n**MANDATORY READ:** Load `references\u002Fcommunity_discussion_formatting.md`\n**MANDATORY READ:** Load [announcement_styles.md](references\u002Fannouncement_styles.md)\n**MANDATORY READ:** Load `references\u002Fhumanizer_checklist.md`\n\n---\n\n## Phase 1: Gather Context\n\n1. Read strategy Section 2 -- verify this qualifies as an announcement\n2. Read `CHANGELOG.md` -- extract the latest entry (or the entry matching `$ARGUMENTS` date if provided)\n3. Read `README.md` -- check current version badge, any WARNING\u002FIMPORTANT callouts\n4. Run: `git log --oneline -20` -- recent commits for context\n5. If `$ARGUMENTS` contains a topic keyword (not a date), use it as the announcement subject\n6. Run: `git diff --name-only` (uncommitted) or `git diff --name-only HEAD~1..HEAD` (last commit) -- build the list of changed files\n7. Read key source files from the diff (max 5 files, prioritize by relevance to `$ARGUMENTS` topic):\n   - Protocol\u002Fguide files in diff -> read full (the substance)\n   - SKILL.md files in diff -> read only changed sections via `git diff -- {file}`\n   - Reference files -> read if substantially changed\n   - Goal: understand the \"why\" behind changes that CHANGELOG doesn't spell out\n\n---\n\n## Phase 2: Classify and Select Style\n\n### 2a. Classify Announcement Type\n\n| Type | Trigger | Emoji |\n|------|---------|-------|\n| **Release** | New version in CHANGELOG | :rocket: |\n| **Breaking Change** | WARNING callout in README or \"breaking\" in CHANGELOG | :warning: |\n| **New Features** | New feature entries in CHANGELOG | :sparkles: |\n| **Architecture** | Structural changes (new categories, plugin splits) | :building_construction: |\n| **Community** | Non-technical updates (events, milestones) | :people_holding_hands: |\n\n### 2b. Select Style\n\nUse the **Style Selection Matrix** from `announcement_styles.md` to pick a primary style based on announcement type. Check the last 3 announcements in Discussions — if they all used the same style, pick a different one for variety.\n\nOptionally mix: use a hook from one style with the body from another (see Mixing Styles table in `announcement_styles.md`).\n\n---\n\n## Phase 3: Compose Announcement\n\nUse the selected style template from `announcement_styles.md` as the structural basis, and `discussion_formatting.md` for GitHub markdown syntax.\n\n**Required elements (all styles):**\n- Add `### Contributors` section after `### What's Next` — thank contributors by @mention if applicable (skip for solo work)\n- Add footer: `*Full changelog: [CHANGELOG.md](https:\u002F\u002Fgithub.com\u002F{owner}\u002F{repo}\u002Fblob\u002F{default_branch}\u002FCHANGELOG.md)*`\n- If breaking change: include migration steps with clear before\u002Fafter in an `> [!IMPORTANT]` alert\n- End with engagement question (per Writing Quality checklist in `announcement_styles.md`)\n\n---\n\n## Phase 4: Fact-Check\n\nBefore presenting to user, verify every verifiable claim in the draft:\n\n1. **Commands & code blocks** -- grep `README.md` for each command\u002Fsnippet in the draft. If command not found -> replace with the actual command. Never invent install\u002Fupdate commands.\n2. **File paths & links** -- verify each linked file exists: `ls {path}`. Remove or fix broken links.\n3. **Numbers** -- verify counts mentioned against actual data: `git diff --name-only | grep -c SKILL.md` or `ls -d ln-*\u002FSKILL.md | wc -l`.\n4. **Feature descriptions** -- re-read the key source file (from Phase 1 step 7) and confirm the draft accurately describes what changed. No hallucinated capabilities.\n5. **Names** -- verify names match actual directory\u002Ffile names in the repo.\n\n6. **Humanizer audit** -- run the audit protocol from `humanizer_checklist.md`. If 3+ AI patterns found, rewrite flagged sections.\n\n**Gate:** If any check fails, fix the draft before proceeding.\n\n---\n\n## Phase 5: Review and Publish\n\nPresent the composed announcement title + body to the user. **Wait for explicit approval before publishing.**\n\nAfter approval, publish via GraphQL using discovery context:\n\n```bash\ngh api graphql -f query='\n  mutation($title: String!, $body: String!, $repoId: ID!, $catId: ID!) {\n    createDiscussion(input: {\n      repositoryId: $repoId,\n      categoryId: $catId,\n      title: $title,\n      body: $body\n    }) {\n      discussion { url }\n    }\n  }\n' -f title=\"TITLE_HERE\" -f body=\"BODY_HERE\" -f repoId=\"{repo.id}\" -f catId=\"{categories.Announcements}\"\n```\n\nReport the discussion URL to the user.\n\n**Note:** Pinning is not available via API -- remind the user to pin manually in GitHub UI if the announcement is important.\n\n---\n\n## Phase 6: Cross-Post (Optional)\n\nIf the announcement is a release or breaking change, suggest:\n1. Create a matching GitHub Release if a version tag exists: `gh release create vX.Y.Z --notes \"See discussion: URL\"`\n2. Update the repo description if the announcement changes the project scope\n\n---\n\n## Definition of Done\n\n- [ ] Context gathered (CHANGELOG, README, git log, key source files)\n- [ ] Announcement type classified + style selected (different from last 3)\n- [ ] Draft composed using selected style template + formatting rules\n- [ ] Writing quality checklist passed (announcement_styles.md)\n- [ ] Fact-checked (commands, paths, numbers, descriptions, names verified)\n- [ ] User approved final draft\n- [ ] Published via GraphQL mutation, URL reported\n\n---\n\n**Version:** 1.0.0\n**Last Updated:** 2026-03-13\n","> **Paths:** File paths (`references\u002F`, `..\u002Fln-*`) are relative to this skill directory.\n\n# ln-912-community-announcer\n\n**Type:** L3 Worker (standalone)\n**Category:** 9XX Community Engagement\nComposes and publishes structured announcements to GitHub Discussions (Announcements category).\n\n---\n\n## Phase 0: GitHub Discovery\n\n**MANDATORY READ:** Load `references\u002Fcommunity_github_discovery.md`\n\nExecute the discovery protocol. Extract:\n- `{owner}\u002F{repo}` for URLs and git commands\n- `repo.id` for GraphQL mutation\n- `categories[\"Announcements\"]` category ID for publishing\n- Verify Announcements category exists\n\nLoad strategy: check `docs\u002Fcommunity_engagement_strategy.md` in target project, fallback to `references\u002Fcommunity_strategy_template.md`. Extract Section 2 (Announcement Triggers) and Section 6 (Tone Guide).\n\n**MANDATORY READ:** Load `references\u002Fcommunity_discussion_formatting.md`\n**MANDATORY READ:** Load [announcement_styles.md](references\u002Fannouncement_styles.md)\n**MANDATORY READ:** Load `references\u002Fhumanizer_checklist.md`\n\n---\n\n## Phase 1: Gather Context\n\n1. Read strategy Section 2 -- verify this qualifies as an announcement\n2. Read `CHANGELOG.md` -- extract the latest entry (or the entry matching `$ARGUMENTS` date if provided)\n3. Read `README.md` -- check current version badge, any WARNING\u002FIMPORTANT callouts\n4. Run: `git log --oneline -20` -- recent commits for context\n5. If `$ARGUMENTS` contains a topic keyword (not a date), use it as the announcement subject\n6. Run: `git diff --name-only` (uncommitted) or `git diff --name-only HEAD~1..HEAD` (last commit) -- build the list of changed files\n7. Read key source files from the diff (max 5 files, prioritize by relevance to `$ARGUMENTS` topic):\n   - Protocol\u002Fguide files in diff -> read full (the substance)\n   - SKILL.md files in diff -> read only changed sections via `git diff -- {file}`\n   - Reference files -> read if substantially changed\n   - Goal: understand the \"why\" behind changes that CHANGELOG doesn't spell out\n\n---\n\n## Phase 2: Classify and Select Style\n\n### 2a. Classify Announcement Type\n\n| Type | Trigger | Emoji |\n|------|---------|-------|\n| **Release** | New version in CHANGELOG | :rocket: |\n| **Breaking Change** | WARNING callout in README or \"breaking\" in CHANGELOG | :warning: |\n| **New Features** | New feature entries in CHANGELOG | :sparkles: |\n| **Architecture** | Structural changes (new categories, plugin splits) | :building_construction: |\n| **Community** | Non-technical updates (events, milestones) | :people_holding_hands: |\n\n### 2b. Select Style\n\nUse the **Style Selection Matrix** from `announcement_styles.md` to pick a primary style based on announcement type. Check the last 3 announcements in Discussions — if they all used the same style, pick a different one for variety.\n\nOptionally mix: use a hook from one style with the body from another (see Mixing Styles table in `announcement_styles.md`).\n\n---\n\n## Phase 3: Compose Announcement\n\nUse the selected style template from `announcement_styles.md` as the structural basis, and `discussion_formatting.md` for GitHub markdown syntax.\n\n**Required elements (all styles):**\n- Add `### Contributors` section after `### What's Next` — thank contributors by @mention if applicable (skip for solo work)\n- Add footer: `*Full changelog: [CHANGELOG.md](https:\u002F\u002Fgithub.com\u002F{owner}\u002F{repo}\u002Fblob\u002F{default_branch}\u002FCHANGELOG.md)*`\n- If breaking change: include migration steps with clear before\u002Fafter in an `> [!IMPORTANT]` alert\n- End with engagement question (per Writing Quality checklist in `announcement_styles.md`)\n\n---\n\n## Phase 4: Fact-Check\n\nBefore presenting to user, verify every verifiable claim in the draft:\n\n1. **Commands & code blocks** -- grep `README.md` for each command\u002Fsnippet in the draft. If command not found -> replace with the actual command. Never invent install\u002Fupdate commands.\n2. **File paths & links** -- verify each linked file exists: `ls {path}`. Remove or fix broken links.\n3. **Numbers** -- verify counts mentioned against actual data: `git diff --name-only | grep -c SKILL.md` or `ls -d ln-*\u002FSKILL.md | wc -l`.\n4. **Feature descriptions** -- re-read the key source file (from Phase 1 step 7) and confirm the draft accurately describes what changed. No hallucinated capabilities.\n5. **Names** -- verify names match actual directory\u002Ffile names in the repo.\n\n6. **Humanizer audit** -- run the audit protocol from `humanizer_checklist.md`. If 3+ AI patterns found, rewrite flagged sections.\n\n**Gate:** If any check fails, fix the draft before proceeding.\n\n---\n\n## Phase 5: Review and Publish\n\nPresent the composed announcement title + body to the user. **Wait for explicit approval before publishing.**\n\nAfter approval, publish via GraphQL using discovery context:\n\n```bash\ngh api graphql -f query='\n  mutation($title: String!, $body: String!, $repoId: ID!, $catId: ID!) {\n    createDiscussion(input: {\n      repositoryId: $repoId,\n      categoryId: $catId,\n      title: $title,\n      body: $body\n    }) {\n      discussion { url }\n    }\n  }\n' -f title=\"TITLE_HERE\" -f body=\"BODY_HERE\" -f repoId=\"{repo.id}\" -f catId=\"{categories.Announcements}\"\n```\n\nReport the discussion URL to the user.\n\n**Note:** Pinning is not available via API -- remind the user to pin manually in GitHub UI if the announcement is important.\n\n---\n\n## Phase 6: Cross-Post (Optional)\n\nIf the announcement is a release or breaking change, suggest:\n1. Create a matching GitHub Release if a version tag exists: `gh release create vX.Y.Z --notes \"See discussion: URL\"`\n2. Update the repo description if the announcement changes the project scope\n\n---\n\n## Definition of Done\n\n- [ ] Context gathered (CHANGELOG, README, git log, key source files)\n- [ ] Announcement type classified + style selected (different from last 3)\n- [ ] Draft composed using selected style template + formatting rules\n- [ ] Writing quality checklist passed (announcement_styles.md)\n- [ ] Fact-checked (commands, paths, numbers, descriptions, names verified)\n- [ ] User approved final draft\n- [ ] Published via GraphQL mutation, URL reported\n\n---\n\n**Version:** 1.0.0\n**Last Updated:** 2026-03-13\n",{"name":5,"license":15,"description":7,"allowed-tools":41,"disable-model-invocation":42},"Read, Grep, Glob, Bash, WebFetch",true,"main","fbfb242f793fdf040f3a1a6b100896c188c228c8","_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fcommunity-engagement\u002Fskills\u002Fln-912-community-announcer",1,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog","https:\u002F\u002Fgithub.com\u002Fvitalikpestov","Listing on crypto exchanges","2026-06-15 22:12:56",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":42},[53,56,59],{"tool":54,"command":55},"npx","npx skills add vitalikpestov\u002FSkills-Catalog --skill ln-912-community-announcer",{"tool":57,"command":58},"bunx","bunx skills add vitalikpestov\u002FSkills-Catalog --skill ln-912-community-announcer",{"tool":60,"command":61},"pnpm","pnpm dlx skills add vitalikpestov\u002FSkills-Catalog --skill ln-912-community-announcer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fcommunity-engagement\u002Fskills\u002Fln-912-community-announcer\u002FSKILL.md",[64,70,74,78,82],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fannouncement_styles.md","REFERENCE","参考文档",7990,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fcommunity-engagement\u002Fskills\u002Fln-912-community-announcer\u002Freferences\u002Fannouncement_styles.md",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fcommunity_discussion_formatting.md",3384,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fcommunity-engagement\u002Fskills\u002Fln-912-community-announcer\u002Freferences\u002Fcommunity_discussion_formatting.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fcommunity_github_discovery.md",2545,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fcommunity-engagement\u002Fskills\u002Fln-912-community-announcer\u002Freferences\u002Fcommunity_github_discovery.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fcommunity_strategy_template.md",5891,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fcommunity-engagement\u002Fskills\u002Fln-912-community-announcer\u002Freferences\u002Fcommunity_strategy_template.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fhumanizer_checklist.md",4325,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fcommunity-engagement\u002Fskills\u002Fln-912-community-announcer\u002Freferences\u002Fhumanizer_checklist.md",[87,131,155,170,193,226],{"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":109,"publishedAt":130},"01M71V1MC994P553631JZSWVYD","solana-dev","Use when user asks to \"build a Solana dapp\", \"write an Anchor program\", \"create a token\", \"debug Solana errors\", \"set up wallet connection\", \"test my Solana program\", \"deploy to devnet\", or \"explain Solana concepts\" (rent, accounts, PDAs, CPIs, etc.). End-to-end Solana development playbook covering wallet connection, Anchor\u002FPinocchio programs, Codama client generation, LiteSVM\u002FMollusk\u002FSurfpool testing, and security checklists. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana\u002Fclient + @solana\u002Freact-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana\u002Fkit for client\u002FRPC code, and @solana\u002Fweb3-compat for legacy boundaries.","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Web3\u002Fsolana-dev\u002Fskill\u002FSKILL.md",[93,98,101,104],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":99,"categoryName":100,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":102,"categoryName":103,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129],"dev","solana dev","solana","Wallet","search","testing","solana cli","kit","MCP","web3","react","create","server","write","playbook","live","security","ui","concepts","toolchain","2026-11-10 13:02:02",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":130},"01M71TYQPHE2YGKTT7DG9QCW3K","generating-trading-signals","Generate trading signals using technical indicators (RSI, MACD, Bollinger Bands, etc.).\nCombines multiple indicators into composite signals with confidence scores.\nUse when analyzing assets for trading opportunities or checking technical indicators.\nTrigger with phrases like \"get trading signals\", \"check indicators\", \"analyze for entry\",\n\"scan for opportunities\", \"generate buy\u002Fsell signals\", or \"technical analysis\".","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Trading-Finance\u002Fgenerating-trading-signals\u002FSKILL.md",[],[138,139,140,141,142,143,144,145,146,147,148,149,34,33,31,150,151,152,153,154],"generating trading signals","signals","trading signals","trading","get","technical indicators","for","scan","rsi","trigger","python","technical","analysis","code","io","check","analyze",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":130},"01M71TY4CR3GKGQ3M12X9WN95Y","prediction-monitor","Prediction Monitor - Auto-activating skill for ML Deployment.\nTriggers on: prediction monitor, prediction monitor\nPart of the ML Deployment skill category.","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Trading-Finance\u002FAI Predictions\u002Fprediction-monitor\u002FSKILL.md",[],[162,163,164,144,165,24,123,166,167,23,168,169,31],"prediction","monitor","prediction monitor","deployment","edit","triggers","auto","ml",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":130},"01M71TXD9MYXZC39HCPP909HTZ","strategy-advisor","High-level strategic thinking and business decision guidance for planning and direction-setting.\nUse when: making strategic decisions, evaluating business options, setting direction, analyzing\ntrade-offs, or when user mentions strategy, business planning, competitive analysis, or long-term planning.","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Product-Apps\u002Fstrategy-advisor\u002FSKILL.md",[],[177,178,179,180,181,182,183,184,185,144,186,187,188,34,189,190,33,191,150,192],"strategy advisor","strategy","advisor","competitive","setting","thinking","planning","direction","trade-offs","long","decision","strategic","business","apps","decisions","trade",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":197,"sourceHtmlUrl":198,"categories":199,"keywords":206,"publishedAt":130},"01M71TWHBT2R1P1FNWTW67ZREP","app-paywall-pilot","Design, audit, debug, and implement App Store-compliant mobile paywalls, subscription flows, pricing screens, trials, offers, feature gates, and subscription lifecycle UX. Use when the user asks to audit my paywall, fix App Store 3.1.2 rejection, improve trial-to-paid, choose plans\u002Fprices\u002Ftrials, review RevenueCat\u002FAdapty\u002FApphud\u002FSuperwall setup, calculate LTV\u002FROAS, or build paywall implementation.","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Product-Apps\u002Ffrom-dosesync\u002Fapp-paywall-pilot\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Product-Apps\u002Ffrom-dosesync\u002Fapp-paywall-pilot\u002FSKILL.md",[200,203],{"categoryNo":201,"categoryName":202,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":204,"categoryName":205,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000032","设计师",[207,208,209,210,211,212,213,214,215,216,217,218,33,219,220,221,222,223,224,225],"app","paywall","app paywall pilot","paid","paywalls","prices","choose","flows","fix","improve","design","app store","review","audit","ux","subscription","mobile","my","calculate",{"skillNo":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":230,"licenseFileUrl":231,"sourceHtmlUrl":232,"categories":233,"keywords":236,"publishedAt":130},"01M71TWET8GFKEB7ZHJPMQX29V","figma","Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Product-Apps\u002Ffigma\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Product-Apps\u002Ffigma\u002FSKILL.md",[234,235],{"categoryNo":102,"categoryName":103,"taxonomyType":96,"taxonomyTypeDesc":97},{"categoryNo":204,"categoryName":205,"taxonomyType":107,"taxonomyTypeDesc":108},[228,237,238,239,240,147,217,118,34,33,241,242,151,243,122,244,245,246,247,248],"fetch","ids","mcp setup","translate","mcp server","Variables","task","Nodes","figma mcp","code implementation","node","assets"]