Use to give an agent a universal identity and reachable channels, a stable handle the agent presents across surfaces, when agents need to be addressable and authenticated rather than anonymous processes.
Claude Code skill that automates mountain route research for North American peaks. Aggregates data from 10+ mountaineering sources like Mountaineers.org, PeakBagger.com and SummitPost.com to generate detailed route beta reports with weather, avalanche conditions, and trip reports.
CLI that detects dead `.claude/rules/` files by checking if `paths:` globs actually match files in your repo. Catches silent rule failures where renamed directories or typos in glob patterns cause rules to never apply. Features CI mode (exit 1 on dead rules), JSON output, and verbose mode showing matched files.
Read-only PostgreSQL query skill for Claude Code. Executes SELECT/SHOW/EXPLAIN/WITH queries across configured databases with strict validation, timeouts, and row limits. Supports multiple connections with descriptions for database selection.
Use to give an agent a queryable wiki knowledge base when memory should be a navigable knowledge graph, not just a flat log: ingest files, folders, and URLs into a linked vault, then search or ask it in natural language.
Use to run many agents in parallel as a visible grid of terminal panes: create an NxM layout, name and monitor panes, broadcast or target prompts, and save/restore whole company configurations.
Armory: a ranked catalog of 64,000+ open-source agent-harness components with a CLI (`armory search|install|init|rank`), an MCP server and a REST API; every row carries one 0–100 score from public signals.
Use to scaffold a complete agent-native harness: the CLAUDE.md, rules, skills, hooks, sub-agents, and memory layout, so a new project starts with the full discipline stack instead of an empty repo.
Use to orchestrate a swarm of sub-agents under a CEO pattern when one agent isn't enough but a full visible grid is overkill: break a mission into roles, dispatch them, and coordinate via signal files.
Use to track and cap what an agent run costs: meter token/compute spend, set budgets, and surface cost as a first-class signal so an autonomous agent doesn't quietly burn through its limit.
Use to apply deterministic, zero-LLM code transforms: fast, repeatable edits that don't need a model, so an agent offloads mechanical changes to a cheap tool instead of spending tokens reasoning through them.
Use to author, test, and share agent skills from the command line: scaffold a SKILL.md, validate its structure, and package it for reuse, turning a one-off procedure into a portable capability.