[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M739ST2YCY13B5CKS82K9QC3":3,"skill-same:01M739ST2YCY13B5CKS82K9QC3":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M739ST2YCY13B5CKS82K9QC3","install-almanac-content",null,"Install skills, agents, and teams from agent-almanac into any supported agentic framework using the CLI. Covers framework detection, content search, installation with dependency resolution, health auditing, and manifest-based syncing. Use when setting up a new project with agentic capabilities, installing specific skills or entire domains, targeting multiple frameworks simultaneously, or maintaining a declarative manifest of installed content.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Finstall-almanac-content\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: install-almanac-content\nlocale: caveman-lite\nsource_locale: en\nsource_commit: 82c77053\ntranslator: \"Julius Brussee homage — caveman\"\ntranslation_date: \"2026-04-24\"\ndescription: >\n  Install skills, agents, and teams from agent-almanac into any supported\n  agentic framework using the CLI. Covers framework detection, content\n  search, installation with dependency resolution, health auditing, and\n  manifest-based syncing. Use when setting up a new project with agentic\n  capabilities, installing specific skills or entire domains, targeting\n  multiple frameworks simultaneously, or maintaining a declarative\n  manifest of installed content.\nlicense: MIT\nallowed-tools:\n  - Bash\n  - Read\n  - Glob\nmetadata:\n  author: Philipp Thoss\n  version: \"1.1\"\n  domain: general\n  complexity: basic\n  language: multi\n  tags:\n    - cli\n    - installation\n    - framework-integration\n    - discovery\n---\n\n# Install Almanac Content\n\nUse the `agent-almanac` CLI to install skills, agents, and teams into any supported agentic framework.\n\n## When to Use\n\n- Setting up a new project and need to install agentic skills, agents, or teams\n- Installing all skills from a specific domain (e.g., `r-packages`, `devops`)\n- Targeting multiple frameworks simultaneously (Claude Code, Cursor, Copilot, etc.)\n- Creating or syncing a declarative `agent-almanac.yml` manifest for reproducible setups\n- Auditing installed content for broken symlinks or stale references\n\n## Inputs\n\n- **Required**: Content to install -- one or more skill, agent, or team IDs (e.g., `create-skill`, `r-developer`, `r-package-review`)\n- **Optional**: `--domain \u003Cdomain>` -- install all skills from a domain instead of naming individual IDs\n- **Optional**: `--framework \u003Cid>` -- target a specific framework (default: auto-detect all)\n- **Optional**: `--with-deps` -- also install agent skills and team agents+skills\n- **Optional**: `--dry-run` -- preview changes without writing to disk\n- **Optional**: `--global` -- install to global scope instead of project scope\n- **Optional**: `--force` -- overwrite existing content\n- **Optional**: `--source \u003Cpath>` -- explicit path to agent-almanac root (default: auto-detect)\n\n## Procedure\n\n### Step 1: Detect Frameworks\n\nRun framework detection to see which agentic tools are present in the current project:\n\n```bash\nagent-almanac detect\n```\n\nThis scans the working directory for configuration files and directories (`.claude\u002F`, `.cursor\u002F`, `.github\u002Fcopilot-instructions\u002F`, `.agents\u002F`, etc.) and reports which frameworks are active.\n\n**Got:** Output lists one or more detected frameworks with their adapter status. If no frameworks are detected, the universal adapter (`.agents\u002Fskills\u002F`) is used as fallback.\n\n**If fail:** If the CLI is not found, ensure it is installed and on PATH. If detection returns nothing and you know a framework is present, use `--framework \u003Cid>` to specify it explicitly. Run `agent-almanac list --domains` to verify the CLI can reach the registries.\n\n### Step 2: Search for Content\n\nFind skills, agents, or teams by keyword:\n\n```bash\nagent-almanac search \u003Ckeyword>\n```\n\nTo browse by category:\n\n```bash\nagent-almanac list --domains          # List all domains with skill counts\nagent-almanac list -d r-packages      # List skills in a specific domain\nagent-almanac list --agents           # List all agents\nagent-almanac list --teams            # List all teams\n```\n\n**Got:** Search results or filtered lists display matching content with IDs and descriptions.\n\n**If fail:** If no results appear, try broader keywords. Verify the almanac root is reachable: `agent-almanac list` should show the full skill count. If it cannot find the root, pass `--source \u002Fpath\u002Fto\u002Fagent-almanac`.\n\n### Step 3: Install Content\n\nInstall one or more items by name:\n\n```bash\n# Install specific skills\nagent-almanac install create-skill write-testthat-tests\n\n# Install all skills from a domain\nagent-almanac install --domain devops\n\n# Install an agent with its skills\nagent-almanac install --agent r-developer --with-deps\n\n# Install a team with its agents and their skills\nagent-almanac install --team r-package-review --with-deps\n\n# Target a specific framework\nagent-almanac install create-skill --framework cursor\n\n# Preview without writing\nagent-almanac install --domain esoteric --dry-run\n\n# Install to global scope\nagent-almanac install create-skill --global\n```\n\nThe CLI resolves the content from the registries, selects the appropriate adapter for each detected framework, and writes files to the framework-specific paths (e.g., `.claude\u002Fskills\u002F` for Claude Code, `.cursor\u002Frules\u002F` for Cursor).\n\n**Got:** Output confirms the number of items installed and the target framework(s). Installed content appears in the correct framework directory.\n\n**If fail:** If items are not found, verify the ID matches the `name` field in the registry (`skills\u002F_registry.yml`, `agents\u002F_registry.yml`, `teams\u002F_registry.yml`). If files already exist and installation is skipped, use `--force` to overwrite.\n\n### Step 4: Verify Installation\n\nRun a health check on all installed content:\n\n```bash\nagent-almanac audit\n```\n\nTo audit a specific framework or scope:\n\n```bash\nagent-almanac audit --framework claude-code\nagent-almanac audit --global\n```\n\nTo see what is currently installed:\n\n```bash\nagent-almanac list --installed\n```\n\n**Got:** Audit reports all installed items as healthy with no broken references. The `--installed` listing shows each item with its type and framework.\n\n**If fail:** If the audit reports broken items, reinstall them with `--force`. If symlinks are broken, verify the almanac source path has not moved. Run `agent-almanac install \u003Cbroken-id> --force` to repair.\n\n### Step 5: Manage with a Manifest (Optional)\n\nFor reproducible setups, use a declarative `agent-almanac.yml` manifest:\n\n```bash\n# Generate a starter manifest\nagent-almanac init\n```\n\nThis creates `agent-almanac.yml` in the current directory with detected frameworks and placeholder content lists. Edit the file to declare desired skills, agents, and teams:\n\n```yaml\nsource: \u002Fpath\u002Fto\u002Fagent-almanac\nframeworks:\n  - claude-code\n  - cursor\nskills:\n  - create-skill\n  - domain:r-packages\nagents:\n  - r-developer\nteams:\n  - r-package-review\n```\n\nThen install everything declared in the manifest:\n\n```bash\nagent-almanac install\n```\n\nTo reconcile installed state with the manifest (install missing, remove extra):\n\n```bash\nagent-almanac sync\nagent-almanac sync --dry-run  # Preview first\n```\n\n**Got:** Running `install` with no arguments reads the manifest and installs all declared content. Running `sync` brings the installed state into alignment with the manifest, adding missing items and removing undeclared ones.\n\n**If fail:** If `sync` reports \"No agent-almanac.yml found\", run `agent-almanac init` first. If the manifest resolves to 0 items, check that skill\u002Fagent\u002Fteam IDs match the registry entries exactly. Comment lines starting with `#` are ignored.\n\n### Step 6: Manage Teams as Campfires (Optional)\n\nThe campfire commands provide a warm, team-oriented alternative to `install --team`:\n\n```bash\n# Browse all available team circles\nagent-almanac campfire --all\n\n# Inspect a specific circle (members, practices, pattern)\nagent-almanac campfire tending\n\n# See shared agents between teams (hearth-keepers)\nagent-almanac campfire --map\n\n# Gather a team (install with arrival ceremony)\nagent-almanac gather tending\nagent-almanac gather tending --ceremonial    # Show each skill arriving\nagent-almanac gather tending --only mystic,gardener  # Partial gathering\n\n# Check fire health (burning \u002F embers \u002F cold)\nagent-almanac tend\n\n# Scatter a team (uninstall with farewell)\nagent-almanac scatter tending\n```\n\nCampfire state is tracked in `.agent-almanac\u002Fstate.json` (git-ignored, local to the project). Fires have thermal states: **burning** (used within 7 days), **embers** (within 30 days), **cold** (30+ days). Running `tend` warms all fires and reports their health.\n\nShared skills are protected during scatter — if a skill is needed by another gathered fire, it remains installed. Shared agents walk between fires rather than being duplicated.\n\nAll campfire commands support `--quiet` (standard reporter output) and `--json` (machine-parseable) for scripting.\n\n**Got:** Teams are gathered and managed with state tracking. `campfire --all` shows fire states. `tend` reports health.\n\n**If fail:** If campfire state is corrupted, delete `.agent-almanac\u002Fstate.json` and re-gather teams. If `gather` fails, check that the team name matches an entry in `teams\u002F_registry.yml`.\n\n## Validation\n\n- [ ] `agent-almanac detect` shows expected frameworks\n- [ ] `agent-almanac list --installed` shows all intended content\n- [ ] `agent-almanac audit` reports no broken items\n- [ ] Installed skills resolve in the target framework (e.g., `\u002Fskill-name` works in Claude Code)\n- [ ] If using a manifest, `agent-almanac sync --dry-run` reports no changes needed\n\n## Pitfalls\n\n- **Forgetting `--with-deps` for agents and teams**: Installing an agent without `--with-deps` installs only the agent definition, not its referenced skills. The agent will be present but unable to follow its skill procedures. Use `--with-deps` for agents and teams unless you have already installed the dependencies separately.\n- **Manifest drift**: After manually installing or removing content, the manifest falls out of sync with the actual installed state. Run `agent-almanac sync` periodically, or install through the manifest to keep them aligned.\n- **Scope confusion (project vs global)**: Content installed with `--global` goes to `~\u002F.claude\u002Fskills\u002F` (or equivalent), while project-scope content goes to `.claude\u002Fskills\u002F` in the current directory. If a skill is not found, check whether it was installed in the wrong scope.\n- **Stale source path**: If the agent-almanac repository is moved or renamed, the `--source` path in manifests and auto-detection will break. Update the `source` field in `agent-almanac.yml` or re-run `agent-almanac init`.\n- **Framework not detected**: The detector looks for specific files and directories. A freshly initialized project may not have these yet. Use `--framework \u003Cid>` explicitly until the project has the expected structure, or rely on the universal adapter.\n- **Campfire thermal state confusion**: Fires go cold after 30 days without use. Running `agent-almanac tend` resets the timer for all gathered fires. If a fire shows as \"cold,\" it is still fully installed — the thermal state reflects recency of use, not installation health.\n\n## Related Skills\n\n- `create-skill` -- author new skills to add to the almanac before installing them\n- `configure-mcp-server` -- set up MCP servers that agents may need after installation\n- `write-claude-md` -- configure CLAUDE.md to reference installed skills\n- `audit-discovery-symlinks` -- diagnose symlink issues for Claude Code skill discovery\n- `design-cli-output` -- terminal output patterns used by the CLI's reporter and campfire ceremony\n","# Install Almanac Content\n\nUse the `agent-almanac` CLI to install skills, agents, and teams into any supported agentic framework.\n\n## When to Use\n\n- Setting up a new project and need to install agentic skills, agents, or teams\n- Installing all skills from a specific domain (e.g., `r-packages`, `devops`)\n- Targeting multiple frameworks simultaneously (Claude Code, Cursor, Copilot, etc.)\n- Creating or syncing a declarative `agent-almanac.yml` manifest for reproducible setups\n- Auditing installed content for broken symlinks or stale references\n\n## Inputs\n\n- **Required**: Content to install -- one or more skill, agent, or team IDs (e.g., `create-skill`, `r-developer`, `r-package-review`)\n- **Optional**: `--domain \u003Cdomain>` -- install all skills from a domain instead of naming individual IDs\n- **Optional**: `--framework \u003Cid>` -- target a specific framework (default: auto-detect all)\n- **Optional**: `--with-deps` -- also install agent skills and team agents+skills\n- **Optional**: `--dry-run` -- preview changes without writing to disk\n- **Optional**: `--global` -- install to global scope instead of project scope\n- **Optional**: `--force` -- overwrite existing content\n- **Optional**: `--source \u003Cpath>` -- explicit path to agent-almanac root (default: auto-detect)\n\n## Procedure\n\n### Step 1: Detect Frameworks\n\nRun framework detection to see which agentic tools are present in the current project:\n\n```bash\nagent-almanac detect\n```\n\nThis scans the working directory for configuration files and directories (`.claude\u002F`, `.cursor\u002F`, `.github\u002Fcopilot-instructions\u002F`, `.agents\u002F`, etc.) and reports which frameworks are active.\n\n**Got:** Output lists one or more detected frameworks with their adapter status. If no frameworks are detected, the universal adapter (`.agents\u002Fskills\u002F`) is used as fallback.\n\n**If fail:** If the CLI is not found, ensure it is installed and on PATH. If detection returns nothing and you know a framework is present, use `--framework \u003Cid>` to specify it explicitly. Run `agent-almanac list --domains` to verify the CLI can reach the registries.\n\n### Step 2: Search for Content\n\nFind skills, agents, or teams by keyword:\n\n```bash\nagent-almanac search \u003Ckeyword>\n```\n\nTo browse by category:\n\n```bash\nagent-almanac list --domains          # List all domains with skill counts\nagent-almanac list -d r-packages      # List skills in a specific domain\nagent-almanac list --agents           # List all agents\nagent-almanac list --teams            # List all teams\n```\n\n**Got:** Search results or filtered lists display matching content with IDs and descriptions.\n\n**If fail:** If no results appear, try broader keywords. Verify the almanac root is reachable: `agent-almanac list` should show the full skill count. If it cannot find the root, pass `--source \u002Fpath\u002Fto\u002Fagent-almanac`.\n\n### Step 3: Install Content\n\nInstall one or more items by name:\n\n```bash\n# Install specific skills\nagent-almanac install create-skill write-testthat-tests\n\n# Install all skills from a domain\nagent-almanac install --domain devops\n\n# Install an agent with its skills\nagent-almanac install --agent r-developer --with-deps\n\n# Install a team with its agents and their skills\nagent-almanac install --team r-package-review --with-deps\n\n# Target a specific framework\nagent-almanac install create-skill --framework cursor\n\n# Preview without writing\nagent-almanac install --domain esoteric --dry-run\n\n# Install to global scope\nagent-almanac install create-skill --global\n```\n\nThe CLI resolves the content from the registries, selects the appropriate adapter for each detected framework, and writes files to the framework-specific paths (e.g., `.claude\u002Fskills\u002F` for Claude Code, `.cursor\u002Frules\u002F` for Cursor).\n\n**Got:** Output confirms the number of items installed and the target framework(s). Installed content appears in the correct framework directory.\n\n**If fail:** If items are not found, verify the ID matches the `name` field in the registry (`skills\u002F_registry.yml`, `agents\u002F_registry.yml`, `teams\u002F_registry.yml`). If files already exist and installation is skipped, use `--force` to overwrite.\n\n### Step 4: Verify Installation\n\nRun a health check on all installed content:\n\n```bash\nagent-almanac audit\n```\n\nTo audit a specific framework or scope:\n\n```bash\nagent-almanac audit --framework claude-code\nagent-almanac audit --global\n```\n\nTo see what is currently installed:\n\n```bash\nagent-almanac list --installed\n```\n\n**Got:** Audit reports all installed items as healthy with no broken references. The `--installed` listing shows each item with its type and framework.\n\n**If fail:** If the audit reports broken items, reinstall them with `--force`. If symlinks are broken, verify the almanac source path has not moved. Run `agent-almanac install \u003Cbroken-id> --force` to repair.\n\n### Step 5: Manage with a Manifest (Optional)\n\nFor reproducible setups, use a declarative `agent-almanac.yml` manifest:\n\n```bash\n# Generate a starter manifest\nagent-almanac init\n```\n\nThis creates `agent-almanac.yml` in the current directory with detected frameworks and placeholder content lists. Edit the file to declare desired skills, agents, and teams:\n\n```yaml\nsource: \u002Fpath\u002Fto\u002Fagent-almanac\nframeworks:\n  - claude-code\n  - cursor\nskills:\n  - create-skill\n  - domain:r-packages\nagents:\n  - r-developer\nteams:\n  - r-package-review\n```\n\nThen install everything declared in the manifest:\n\n```bash\nagent-almanac install\n```\n\nTo reconcile installed state with the manifest (install missing, remove extra):\n\n```bash\nagent-almanac sync\nagent-almanac sync --dry-run  # Preview first\n```\n\n**Got:** Running `install` with no arguments reads the manifest and installs all declared content. Running `sync` brings the installed state into alignment with the manifest, adding missing items and removing undeclared ones.\n\n**If fail:** If `sync` reports \"No agent-almanac.yml found\", run `agent-almanac init` first. If the manifest resolves to 0 items, check that skill\u002Fagent\u002Fteam IDs match the registry entries exactly. Comment lines starting with `#` are ignored.\n\n### Step 6: Manage Teams as Campfires (Optional)\n\nThe campfire commands provide a warm, team-oriented alternative to `install --team`:\n\n```bash\n# Browse all available team circles\nagent-almanac campfire --all\n\n# Inspect a specific circle (members, practices, pattern)\nagent-almanac campfire tending\n\n# See shared agents between teams (hearth-keepers)\nagent-almanac campfire --map\n\n# Gather a team (install with arrival ceremony)\nagent-almanac gather tending\nagent-almanac gather tending --ceremonial    # Show each skill arriving\nagent-almanac gather tending --only mystic,gardener  # Partial gathering\n\n# Check fire health (burning \u002F embers \u002F cold)\nagent-almanac tend\n\n# Scatter a team (uninstall with farewell)\nagent-almanac scatter tending\n```\n\nCampfire state is tracked in `.agent-almanac\u002Fstate.json` (git-ignored, local to the project). Fires have thermal states: **burning** (used within 7 days), **embers** (within 30 days), **cold** (30+ days). Running `tend` warms all fires and reports their health.\n\nShared skills are protected during scatter — if a skill is needed by another gathered fire, it remains installed. Shared agents walk between fires rather than being duplicated.\n\nAll campfire commands support `--quiet` (standard reporter output) and `--json` (machine-parseable) for scripting.\n\n**Got:** Teams are gathered and managed with state tracking. `campfire --all` shows fire states. `tend` reports health.\n\n**If fail:** If campfire state is corrupted, delete `.agent-almanac\u002Fstate.json` and re-gather teams. If `gather` fails, check that the team name matches an entry in `teams\u002F_registry.yml`.\n\n## Validation\n\n- [ ] `agent-almanac detect` shows expected frameworks\n- [ ] `agent-almanac list --installed` shows all intended content\n- [ ] `agent-almanac audit` reports no broken items\n- [ ] Installed skills resolve in the target framework (e.g., `\u002Fskill-name` works in Claude Code)\n- [ ] If using a manifest, `agent-almanac sync --dry-run` reports no changes needed\n\n## Pitfalls\n\n- **Forgetting `--with-deps` for agents and teams**: Installing an agent without `--with-deps` installs only the agent definition, not its referenced skills. The agent will be present but unable to follow its skill procedures. Use `--with-deps` for agents and teams unless you have already installed the dependencies separately.\n- **Manifest drift**: After manually installing or removing content, the manifest falls out of sync with the actual installed state. Run `agent-almanac sync` periodically, or install through the manifest to keep them aligned.\n- **Scope confusion (project vs global)**: Content installed with `--global` goes to `~\u002F.claude\u002Fskills\u002F` (or equivalent), while project-scope content goes to `.claude\u002Fskills\u002F` in the current directory. If a skill is not found, check whether it was installed in the wrong scope.\n- **Stale source path**: If the agent-almanac repository is moved or renamed, the `--source` path in manifests and auto-detection will break. Update the `source` field in `agent-almanac.yml` or re-run `agent-almanac init`.\n- **Framework not detected**: The detector looks for specific files and directories. A freshly initialized project may not have these yet. Use `--framework \u003Cid>` explicitly until the project has the expected structure, or rely on the universal adapter.\n- **Campfire thermal state confusion**: Fires go cold after 30 days without use. Running `agent-almanac tend` resets the timer for all gathered fires. If a fire shows as \"cold,\" it is still fully installed — the thermal state reflects recency of use, not installation health.\n\n## Related Skills\n\n- `create-skill` -- author new skills to add to the almanac before installing them\n- `configure-mcp-server` -- set up MCP servers that agents may need after installation\n- `write-claude-md` -- configure CLAUDE.md to reference installed skills\n- `audit-discovery-symlinks` -- diagnose symlink issues for Claude Code skill discovery\n- `design-cli-output` -- terminal output patterns used by the CLI's reporter and campfire ceremony\n",{"name":5,"locale":23,"license":14,"metadata":24,"translator":35,"description":36,"allowed-tools":37,"source_commit":41,"source_locale":42,"translation_date":43},"caveman-lite",{"tags":25,"author":30,"domain":31,"version":32,"language":33,"complexity":34},[26,27,28,29],"cli","installation","framework-integration","discovery","Philipp Thoss","general","1.1","multi","basic","Julius Brussee homage — caveman","Install skills, agents, and teams from agent-almanac into any supported agentic framework using the CLI. Covers framework detection, content search, installation with dependency resolution, health auditing, and manifest-based syncing. Use when setting up a new project with agentic capabilities, installing specific skills or entire domains, targeting multiple frameworks simultaneously, or maintaining a declarative manifest of installed content.\n",[38,39,40],"Bash","Read","Glob","82c77053","en","2026-04-24","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Finstall-almanac-content",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add roohe\u002Fagentic-super-skills --skill install-almanac-content",{"tool":58,"command":59},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill install-almanac-content",{"tool":61,"command":62},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill install-almanac-content","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Finstall-almanac-content\u002FSKILL.md",true,[],[67,74,81,88,95,102],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]