install-almanac-content
About
This CLI tool installs pre-built skills, agents, and teams from the agent-almanac repository into your project's agentic framework. It automatically detects your framework, resolves dependencies, and can sync installations using a declarative manifest. Use it to quickly bootstrap agentic capabilities or maintain consistent environments across projects.
Quick Install
Claude Code
Recommendednpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/install-almanac-contentCopy and paste this command in Claude Code to install this skill
Documentation
Install Almanac Content
agent-almanac CLI → install skills/agents/teams into agentic frameworks.
Use When
- New project → agentic skills/agents/teams
- All skills from domain (
r-packages,devops) - Multi-framework (Claude Code, Cursor, Copilot)
- Declarative
agent-almanac.ymlmanifest for reproducible - Audit installed content for broken symlinks / stale refs
In
- Required: content to install (skill/agent/team IDs, e.g.,
create-skill,r-developer,r-package-review) - Optional:
--domain <domain>→ install all skills from domain - Optional:
--framework <id>→ target specific (default: auto-detect all) - Optional:
--with-deps→ install agent skills + team agents+skills - Optional:
--dry-run→ preview no write - Optional:
--global→ global scope not project - Optional:
--force→ overwrite existing - Optional:
--source <path>→ explicit almanac root
Do
Step 1: Detect frameworks
agent-almanac detect
Scans cwd for config files/dirs (.claude/, .cursor/, .github/copilot-instructions/, .agents/) + reports active.
→ Lists detected frameworks w/ adapter status. None → universal adapter (.agents/skills/) fallback.
If err: CLI not found → install + PATH. Detection nothing but framework present → --framework <id> explicit. Run agent-almanac list --domains → verify CLI reaches registries.
Step 2: Search
agent-almanac search <keyword>
Browse by category:
agent-almanac list --domains # List all domains with skill counts
agent-almanac list -d r-packages # List skills in a specific domain
agent-almanac list --agents # List all agents
agent-almanac list --teams # List all teams
→ Results / filtered lists w/ IDs + descriptions.
If err: no results → broader keyword. Verify almanac root: agent-almanac list shows full count. No root → --source /path/to/agent-almanac.
Step 3: Install
# Install specific skills
agent-almanac install create-skill write-testthat-tests
# Install all skills from a domain
agent-almanac install --domain devops
# Install an agent with its skills
agent-almanac install --agent r-developer --with-deps
# Install a team with its agents and their skills
agent-almanac install --team r-package-review --with-deps
# Target a specific framework
agent-almanac install create-skill --framework cursor
# Preview without writing
agent-almanac install --domain esoteric --dry-run
# Install to global scope
agent-almanac install create-skill --global
CLI resolves from registries, selects adapter per framework, writes to framework-specific paths (.claude/skills/ for Claude Code, .cursor/rules/ for Cursor).
→ Output confirms # items + target framework. Content in correct dir.
If err: not found → verify ID matches name field in skills/_registry.yml / agents/_registry.yml / teams/_registry.yml. Files exist + skipped → --force.
Step 4: Verify install
agent-almanac audit
Audit specific framework/scope:
agent-almanac audit --framework claude-code
agent-almanac audit --global
See installed:
agent-almanac list --installed
→ Audit → all healthy, no broken refs. --installed shows each w/ type + framework.
If err: broken → reinstall w/ --force. Broken symlinks → verify almanac source path not moved. Repair: agent-almanac install <broken-id> --force.
Step 5: Manifest (opt)
# Generate a starter manifest
agent-almanac init
Creates agent-almanac.yml w/ detected frameworks + placeholder content. Edit:
source: /path/to/agent-almanac
frameworks:
- claude-code
- cursor
skills:
- create-skill
- domain:r-packages
agents:
- r-developer
teams:
- r-package-review
Install from manifest:
agent-almanac install
Reconcile installed w/ manifest (install missing, remove extra):
agent-almanac sync
agent-almanac sync --dry-run # Preview first
→ install no args reads manifest + installs all. sync aligns state w/ manifest (adds missing, removes undeclared).
If err: sync "No agent-almanac.yml" → agent-almanac init first. 0 items → check IDs match registry exactly. # lines ignored.
Step 6: Teams as campfires (opt)
Warm team-oriented alternative to install --team:
# Browse all available team circles
agent-almanac campfire --all
# Inspect a specific circle (members, practices, pattern)
agent-almanac campfire tending
# See shared agents between teams (hearth-keepers)
agent-almanac campfire --map
# Gather a team (install with arrival ceremony)
agent-almanac gather tending
agent-almanac gather tending --ceremonial # Show each skill arriving
agent-almanac gather tending --only mystic,gardener # Partial gathering
# Check fire health (burning / embers / cold)
agent-almanac tend
# Scatter a team (uninstall with farewell)
agent-almanac scatter tending
State tracked in .agent-almanac/state.json (git-ignored, local). Thermal states: burning (used <7 days), embers (<30 days), cold (30+). tend warms all fires + reports health.
Shared skills protected during scatter — needed by another gathered fire → remains. Shared agents walk between fires not duplicated.
All campfire support --quiet (standard reporter) + --json (machine-parseable) for scripting.
→ Teams gathered + managed w/ state. campfire --all shows states. tend reports health.
If err: state corrupted → delete .agent-almanac/state.json + re-gather. gather fails → team name must match teams/_registry.yml.
Check
-
agent-almanac detectshows expected frameworks -
agent-almanac list --installedshows intended content -
agent-almanac auditno broken - Installed skills resolve in framework (e.g.,
/skill-nameworks) -
agent-almanac sync --dry-runno changes needed (if manifest)
Traps
- Forget
--with-depsfor agents + teams: installs only def, not skills. Agent present but can't follow procedures. Always--with-depsunless deps already installed. - Manifest drift: manual install/remove → out of sync. Run
syncperiodically or always install through manifest. - Scope confusion (project vs global):
--global→~/.claude/skills/. Project →.claude/skills/in cwd. Not found → check scope. - Stale source path: repo moved/renamed →
--sourcein manifests + auto-detect breaks. Updatesourceinagent-almanac.ymlor re-runinit. - Framework not detected: detector looks for specific files/dirs. Fresh project may lack →
--framework <id>explicit or rely on universal. - Campfire thermal confusion: fires cold after 30 days.
tendresets timer. Cold ≠ broken install — state reflects recency of use, not install health.
→
create-skill— author new skills before installconfigure-mcp-server— MCP servers agents may need post-installwrite-claude-md— reference installed skills in CLAUDE.mdaudit-discovery-symlinks— diagnose symlink issues for Claude Code discoverydesign-cli-output— terminal patterns used by reporter + campfire ceremony
GitHub Repository
Related Skills
content-collections
MetaThis skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
polymarket
MetaThis skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.
creating-opencode-plugins
MetaThis skill helps developers create OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It provides the plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript modules. Use it when you need to intercept, monitor, or extend the OpenCode AI assistant's lifecycle with custom event-driven logic.
sglang
MetaSGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.
