[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FBSK709DGQNEXTH9K6ETWF":3,"skill-same:01M6FBSK709DGQNEXTH9K6ETWF":70},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":30,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6FBSK709DGQNEXTH9K6ETWF","source-driven-development",null,"Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.","boisenoise\u002Fskills-collections","boisenoise","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F193180?v=4","01M6CDBDQK6BDN55ZMA6B6PKBM","01M6CDBDVSJ3JPTBYN26FZ7TZK",12,"MIT","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-source-driven-development\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"source","development","source driven development","driven","implementation","when","tree","correctness","you","with","free","critical","main","community","github","agent-skills","use","decision","https","license","code","documentation","official","2026-11-10 10:12:30",false,"---\nname: source-driven-development\ndescription: Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Faddyosmani\u002Fagent-skills\u002Ftree\u002Fmain\u002Fskills\u002Fsource-driven-development\nsource_repo: addyosmani\u002Fagent-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Faddyosmani\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Source-Driven Development\n\n## Overview\n\nEvery framework-specific code decision must be backed by official documentation. Don't implement from memory — verify, cite, and let the user see your sources. Training data goes stale, APIs get deprecated, best practices evolve. This skill ensures the user gets code they can trust because every pattern traces back to an authoritative source they can check.\n\n## When to Use\n\n- The user wants code that follows current best practices for a given framework\n- Building boilerplate, starter code, or patterns that will be copied across a project\n- The user explicitly asks for documented, verified, or \"correct\" implementation\n- Implementing features where the framework's recommended approach matters (forms, routing, data fetching, state management, auth)\n- Reviewing or improving code that uses framework-specific patterns\n- Any time you are about to write framework-specific code from memory\n\n**When NOT to use:**\n\n- Correctness does not depend on a specific version (renaming variables, fixing typos, moving files)\n- Pure logic that works the same across all versions (loops, conditionals, data structures)\n- The user explicitly wants speed over verification (\"just do it quickly\")\n\n## The Process\n\n```\nDETECT ──→ FETCH ──→ IMPLEMENT ──→ CITE\n  │          │           │            │\n  ▼          ▼           ▼            ▼\n What       Get the    Follow the   Show your\n stack?     relevant   documented   sources\n            docs       patterns\n```\n\n### Step 1: Detect Stack and Versions\n\nRead dependency manifests plus lockfiles\u002Finstalled metadata to identify resolved versions; version ranges alone do not establish exact installed versions:\n\n```\npackage.json    → Node\u002FReact\u002FVue\u002FAngular\u002FSvelte\ncomposer.json   → PHP\u002FSymfony\u002FLaravel\nrequirements.txt \u002F pyproject.toml → Python\u002FDjango\u002FFlask\ngo.mod          → Go\nCargo.toml      → Rust\nGemfile         → Ruby\u002FRails\n```\n\nState what you found explicitly:\n\n```\nSTACK DETECTED:\n- React 19.1.0 (from package.json)\n- Vite 6.2.0\n- Tailwind CSS 4.0.3\n→ Fetching official docs for the relevant patterns.\n```\n\nIf versions are missing or ambiguous, **ask the user**. Don't guess — the version determines which patterns are correct.\n\n### Step 2: Fetch Official Documentation\n\nFetch the specific documentation page for the feature you're implementing. Not the homepage, not the full docs — the relevant page.\n\n**Source hierarchy (in order of authority):**\n\n| Priority | Source | Example |\n|----------|--------|---------|\n| 1 | Official documentation | react.dev, docs.djangoproject.com, symfony.com\u002Fdoc |\n| 2 | Official blog \u002F changelog | react.dev\u002Fblog, nextjs.org\u002Fblog |\n| 3 | Web standards references | MDN, web.dev, html.spec.whatwg.org |\n| 4 | Browser\u002Fruntime compatibility | caniuse.com, node.green |\n\n**Not authoritative — never cite as primary sources:**\n\n- Stack Overflow answers\n- Blog posts or tutorials (even popular ones)\n- AI-generated documentation or summaries\n- Your own training data (that is the whole point — verify it)\n\n**Be precise with what you fetch:**\n\n```\nBAD:  Fetch the React homepage\nGOOD: Fetch react.dev\u002Freference\u002Freact\u002FuseActionState\n\nBAD:  Search \"django authentication best practices\"\nGOOD: Fetch docs.djangoproject.com\u002Fen\u002F6.0\u002Ftopics\u002Fauth\u002F\n```\n\nAfter fetching, extract the key patterns and note any deprecation warnings or migration guidance.\n\nWhen official sources conflict with each other (e.g. a migration guide contradicts the API reference), surface the discrepancy to the user and verify which pattern actually works against the detected version.\n\n### Step 3: Implement Following Documented Patterns\n\nWrite code that matches what the documentation shows:\n\n- Use the API signatures from the docs, not from memory\n- Use documented patterns compatible with the installed version and local requirements; a newer API is not by itself a reason for an unrelated migration\n- If the docs deprecate a pattern, don't use the deprecated version\n- If the docs don't cover something, flag it as unverified\n\n**When docs conflict with existing project code:**\n\n```\nCONFLICT DETECTED:\nThe existing codebase uses useState for form loading state,\nbut React 19 docs recommend useActionState for this pattern.\n(Source: react.dev\u002Freference\u002Freact\u002FuseActionState)\n\nOptions:\nA) Use the modern pattern (useActionState) — consistent with current docs\nB) Match existing code (useState) — consistent with codebase\n→ Which approach do you prefer?\n```\n\nSurface the conflict. Don't silently pick one.\n\n### Step 4: Cite Your Sources\n\nEvery framework-specific pattern gets a citation. The user must be able to verify every decision.\n\n**In code comments:**\n\n```typescript\n\u002F\u002F React 19 form handling with useActionState\n\u002F\u002F Source: https:\u002F\u002Freact.dev\u002Freference\u002Freact\u002FuseActionState#usage\nconst [state, formAction, isPending] = useActionState(submitOrder, initialState);\n```\n\n**In conversation:**\n\n```\nI'm using useActionState instead of manual useState for the\nform submission state. React 19 provides this hook for supported Action patterns; manual\nstate remains valid where appropriate.\n\nSource: https:\u002F\u002Freact.dev\u002Fblog\u002F2024\u002F12\u002F05\u002Freact-19#actions\n\"useTransition now supports async functions [...] to handle\npending states automatically\"\n```\n\n**Citation rules:**\n\n- Full URLs, not shortened\n- Prefer deep links with anchors where possible (e.g. `\u002FuseActionState#usage` over `\u002FuseActionState`) — anchors survive doc restructuring better than top-level pages\n- Quote the relevant passage when it supports a non-obvious decision\n- Include browser\u002Fruntime support data when recommending platform features\n- If you cannot find documentation for a pattern, say so explicitly:\n\n```\nUNVERIFIED: I could not find official documentation for this\npattern. This is based on training data and may be outdated.\nVerify before using in production.\n```\n\nHonesty about what you couldn't verify is more valuable than false confidence.\n\n## Common Rationalizations\n\n| Rationalization | Reality |\n|---|---|\n| \"I'm confident about this API\" | Confidence is not evidence. Training data contains outdated patterns that look correct but break against current versions. Verify. |\n| \"Fetching docs wastes tokens\" | Hallucinating an API wastes more. The user debugs for an hour, then discovers the function signature changed. One fetch prevents hours of rework. |\n| \"The docs won't have what I need\" | If the docs don't cover it, that's valuable information — the pattern may not be officially recommended. |\n| \"I'll just mention it might be outdated\" | A disclaimer doesn't help. Either verify and cite, or clearly flag it as unverified. Hedging is the worst option. |\n| \"This is a simple task, no need to check\" | Simple tasks with wrong patterns become templates. The user copies your deprecated form handler into ten components before discovering the modern approach exists. |\n\n## Red Flags\n\n- Writing framework-specific code without checking the docs for that version\n- Using \"I believe\" or \"I think\" about an API instead of citing the source\n- Implementing a pattern without knowing which version it applies to\n- Citing Stack Overflow or blog posts instead of official documentation\n- Using deprecated APIs because they appear in training data\n- Not reading `package.json` \u002F dependency files before implementing\n- Delivering code without source citations for framework-specific decisions\n- Fetching an entire docs site when only one page is relevant\n\n## Verification\n\nAfter implementing with source-driven development:\n\n- [ ] Framework and library versions were identified from the dependency file\n- [ ] Official documentation was fetched for framework-specific patterns\n- [ ] All sources are official documentation, not blog posts or training data\n- [ ] Code follows the patterns shown in the current version's documentation\n- [ ] Non-trivial decisions include source citations with full URLs\n- [ ] No deprecated APIs are used (checked against migration guides)\n- [ ] Conflicts between docs and existing code were surfaced to the user\n- [ ] Anything that could not be verified is explicitly flagged as unverified\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Source-Driven Development\n\n## Overview\n\nEvery framework-specific code decision must be backed by official documentation. Don't implement from memory — verify, cite, and let the user see your sources. Training data goes stale, APIs get deprecated, best practices evolve. This skill ensures the user gets code they can trust because every pattern traces back to an authoritative source they can check.\n\n## When to Use\n\n- The user wants code that follows current best practices for a given framework\n- Building boilerplate, starter code, or patterns that will be copied across a project\n- The user explicitly asks for documented, verified, or \"correct\" implementation\n- Implementing features where the framework's recommended approach matters (forms, routing, data fetching, state management, auth)\n- Reviewing or improving code that uses framework-specific patterns\n- Any time you are about to write framework-specific code from memory\n\n**When NOT to use:**\n\n- Correctness does not depend on a specific version (renaming variables, fixing typos, moving files)\n- Pure logic that works the same across all versions (loops, conditionals, data structures)\n- The user explicitly wants speed over verification (\"just do it quickly\")\n\n## The Process\n\n```\nDETECT ──→ FETCH ──→ IMPLEMENT ──→ CITE\n  │          │           │            │\n  ▼          ▼           ▼            ▼\n What       Get the    Follow the   Show your\n stack?     relevant   documented   sources\n            docs       patterns\n```\n\n### Step 1: Detect Stack and Versions\n\nRead dependency manifests plus lockfiles\u002Finstalled metadata to identify resolved versions; version ranges alone do not establish exact installed versions:\n\n```\npackage.json    → Node\u002FReact\u002FVue\u002FAngular\u002FSvelte\ncomposer.json   → PHP\u002FSymfony\u002FLaravel\nrequirements.txt \u002F pyproject.toml → Python\u002FDjango\u002FFlask\ngo.mod          → Go\nCargo.toml      → Rust\nGemfile         → Ruby\u002FRails\n```\n\nState what you found explicitly:\n\n```\nSTACK DETECTED:\n- React 19.1.0 (from package.json)\n- Vite 6.2.0\n- Tailwind CSS 4.0.3\n→ Fetching official docs for the relevant patterns.\n```\n\nIf versions are missing or ambiguous, **ask the user**. Don't guess — the version determines which patterns are correct.\n\n### Step 2: Fetch Official Documentation\n\nFetch the specific documentation page for the feature you're implementing. Not the homepage, not the full docs — the relevant page.\n\n**Source hierarchy (in order of authority):**\n\n| Priority | Source | Example |\n|----------|--------|---------|\n| 1 | Official documentation | react.dev, docs.djangoproject.com, symfony.com\u002Fdoc |\n| 2 | Official blog \u002F changelog | react.dev\u002Fblog, nextjs.org\u002Fblog |\n| 3 | Web standards references | MDN, web.dev, html.spec.whatwg.org |\n| 4 | Browser\u002Fruntime compatibility | caniuse.com, node.green |\n\n**Not authoritative — never cite as primary sources:**\n\n- Stack Overflow answers\n- Blog posts or tutorials (even popular ones)\n- AI-generated documentation or summaries\n- Your own training data (that is the whole point — verify it)\n\n**Be precise with what you fetch:**\n\n```\nBAD:  Fetch the React homepage\nGOOD: Fetch react.dev\u002Freference\u002Freact\u002FuseActionState\n\nBAD:  Search \"django authentication best practices\"\nGOOD: Fetch docs.djangoproject.com\u002Fen\u002F6.0\u002Ftopics\u002Fauth\u002F\n```\n\nAfter fetching, extract the key patterns and note any deprecation warnings or migration guidance.\n\nWhen official sources conflict with each other (e.g. a migration guide contradicts the API reference), surface the discrepancy to the user and verify which pattern actually works against the detected version.\n\n### Step 3: Implement Following Documented Patterns\n\nWrite code that matches what the documentation shows:\n\n- Use the API signatures from the docs, not from memory\n- Use documented patterns compatible with the installed version and local requirements; a newer API is not by itself a reason for an unrelated migration\n- If the docs deprecate a pattern, don't use the deprecated version\n- If the docs don't cover something, flag it as unverified\n\n**When docs conflict with existing project code:**\n\n```\nCONFLICT DETECTED:\nThe existing codebase uses useState for form loading state,\nbut React 19 docs recommend useActionState for this pattern.\n(Source: react.dev\u002Freference\u002Freact\u002FuseActionState)\n\nOptions:\nA) Use the modern pattern (useActionState) — consistent with current docs\nB) Match existing code (useState) — consistent with codebase\n→ Which approach do you prefer?\n```\n\nSurface the conflict. Don't silently pick one.\n\n### Step 4: Cite Your Sources\n\nEvery framework-specific pattern gets a citation. The user must be able to verify every decision.\n\n**In code comments:**\n\n```typescript\n\u002F\u002F React 19 form handling with useActionState\n\u002F\u002F Source: https:\u002F\u002Freact.dev\u002Freference\u002Freact\u002FuseActionState#usage\nconst [state, formAction, isPending] = useActionState(submitOrder, initialState);\n```\n\n**In conversation:**\n\n```\nI'm using useActionState instead of manual useState for the\nform submission state. React 19 provides this hook for supported Action patterns; manual\nstate remains valid where appropriate.\n\nSource: https:\u002F\u002Freact.dev\u002Fblog\u002F2024\u002F12\u002F05\u002Freact-19#actions\n\"useTransition now supports async functions [...] to handle\npending states automatically\"\n```\n\n**Citation rules:**\n\n- Full URLs, not shortened\n- Prefer deep links with anchors where possible (e.g. `\u002FuseActionState#usage` over `\u002FuseActionState`) — anchors survive doc restructuring better than top-level pages\n- Quote the relevant passage when it supports a non-obvious decision\n- Include browser\u002Fruntime support data when recommending platform features\n- If you cannot find documentation for a pattern, say so explicitly:\n\n```\nUNVERIFIED: I could not find official documentation for this\npattern. This is based on training data and may be outdated.\nVerify before using in production.\n```\n\nHonesty about what you couldn't verify is more valuable than false confidence.\n\n## Common Rationalizations\n\n| Rationalization | Reality |\n|---|---|\n| \"I'm confident about this API\" | Confidence is not evidence. Training data contains outdated patterns that look correct but break against current versions. Verify. |\n| \"Fetching docs wastes tokens\" | Hallucinating an API wastes more. The user debugs for an hour, then discovers the function signature changed. One fetch prevents hours of rework. |\n| \"The docs won't have what I need\" | If the docs don't cover it, that's valuable information — the pattern may not be officially recommended. |\n| \"I'll just mention it might be outdated\" | A disclaimer doesn't help. Either verify and cite, or clearly flag it as unverified. Hedging is the worst option. |\n| \"This is a simple task, no need to check\" | Simple tasks with wrong patterns become templates. The user copies your deprecated form handler into ten components before discovering the modern approach exists. |\n\n## Red Flags\n\n- Writing framework-specific code without checking the docs for that version\n- Using \"I believe\" or \"I think\" about an API instead of citing the source\n- Implementing a pattern without knowing which version it applies to\n- Citing Stack Overflow or blog posts instead of official documentation\n- Using deprecated APIs because they appear in training data\n- Not reading `package.json` \u002F dependency files before implementing\n- Delivering code without source citations for framework-specific decisions\n- Fetching an entire docs site when only one page is relevant\n\n## Verification\n\nAfter implementing with source-driven development:\n\n- [ ] Framework and library versions were identified from the dependency file\n- [ ] Official documentation was fetched for framework-specific patterns\n- [ ] All sources are official documentation, not blog posts or training data\n- [ ] Code follows the patterns shown in the current version's documentation\n- [ ] Non-trivial decisions include source citations with full URLs\n- [ ] No deprecated APIs are used (checked against migration guides)\n- [ ] Conflicts between docs and existing code were surfaced to the user\n- [ ] Anything that could not be verified is explicitly flagged as unverified\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":29,"source":46,"license":14,"date_added":47,"description":7,"source_repo":48,"source_type":31,"license_source":49},"https:\u002F\u002Fgithub.com\u002Faddyosmani\u002Fagent-skills\u002Ftree\u002Fmain\u002Fskills\u002Fsource-driven-development",1782864000000,"addyosmani\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Faddyosmani\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE","7bf2279c8a65758319526a721d5c4b75683aec9c","skills\u002Fantigravity-source-driven-development",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-12 14:21:24",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add boisenoise\u002Fskills-collections --skill source-driven-development",{"tool":62,"command":63},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill source-driven-development",{"tool":65,"command":66},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill source-driven-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-source-driven-development\u002FSKILL.md",true,[],[71,96,120,145,164,187],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":41},"01M6WNH92BHVFXHGPDZCPJ0AG0","web-access","Use Treg for public web or platform data only when existing search, browser and connected tools cannot cover the task, with explicit cost and data boundaries.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FSKILL.md",[],[80,81,82,40,19,83,84,85,86,87,88,89,90,91,92,29,28,93,94,23,95],"web","access","web access","browser","search","data","Tools","read","fetch","only","youtube","free tools","platform","cover","normal","2026",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":108,"publishedAt":41},"01M6WNF9XAYAB2CZDDJBAKNM93","treg","Use the Treg CLI or MCP catalog to discover, price and call authorized external tools with team-scoped credentials and a user-approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FSKILL.md",[103],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[98,109,110,32,40,19,37,86,111,112,113,114,34,115,116,29,117,27,118,119,95],"MCP","cli","Budget","credentials","team","catalog","call","discover","external tools","scoped","blob",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":132,"publishedAt":41},"01M6WN93MEAZ4E41DYAHJRPHQT","recruit","Turn a job description into an evidence-linked candidate shortlist through Treg, with job-related ranking and optional authorized business contact enrichment.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FSKILL.md",[127],{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[122,32,40,37,36,133,134,135,136,137,29,138,139,140,27,141,142,143,144,119,98,95],"email","enrichment","business","evidence","phone","ranking","post","job description","for","person","candidate","reason",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":149,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":41},"01M6WN8R5RXSMHM9B4D9FAFX42","rea-growth","Analyze a company’s public growth and content through Treg, distinguish observations from hypotheses, and produce an evidence-linked playbook within an approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FSKILL.md",[],[153,154,155,32,40,37,156,157,36,158,111,159,160,161,136,29,162,163,119,98,95],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","public","observations","company",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":41},"01M6WN2EVE3RQRGWAKBT4S7YT2","make-ugc","Create original AI UGC-style product videos through Treg: research hooks, approve a licensed presenter and voice, generate clips, add captions and report costs.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FSKILL.md",[],[172,173,32,174,40,175,37,176,177,178,179,180,29,181,182,183,184,185,186,119],"make","make ugc","research","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":191,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":41},"01M6WN10ARAA63Y8K1YNGXJ2RM","lead-signals","Find and qualify public buying signals through Treg, rank fitting business accounts and optionally enrich authorized business contact information.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FSKILL.md",[],[195,196,197,32,40,37,198,199,135,200,201,29,202,203,204,205,206,207,208,119],"signals","lead","lead signals","how","find","ready","as","how to","qualify","people","information","enrich","changes","funding"]