Agent skills you can check before you install
Public SKILL.md skills from GitHub repositories with 50+ stars and from the vendors themselves, scanned and scored. Install any of them with one command in Claude Code, Cursor, Codex, GitHub Copilot or Gemini CLI.
49,492 skills from 2,391 repositories · updated 8 hours ago
48,451 skills
- reliability-reporthoangsonww/Claude-Code-Agent-MonitorGenerate a CCAM reliability report from session outcomes, hook events, alerts, tool failures, and data freshness. Use for health reviews, incident follow-up, hook-delivery audits, or reliability trend summaries.ProductivityNo warnings★ 1.1K↓ —
- hook-failure-audithoangsonww/Claude-Code-Agent-MonitorAudit hook delivery health from Agent Monitor data — balance PreToolUse vs PostToolUse (a gap means tools that started but never reported back), detect missing Stop/SubagentStop terminators (sessions/subagents that never closed), and check for stale ingestion (no recent events). Use when hooks look unreliable or events seem to be dropping.OtherNo warnings★ 1.1K↓ —
- audit-agentsdzhng/skillsAudit or rewrite AGENTS.md so it holds only lasting principles. Run it only when the user asks for it by name; never invoke it on your own.OtherNo warnings★ 1.4K↓ —
- daily-standuphoangsonww/Claude-Code-Agent-MonitorGenerate a daily standup summary from recent Claude Code sessions — completed work grouped by project (cwd), session costs from the pricing engine, tool invocations, error/compaction/APIError events, and turn velocity metrics from session metadata (turn_count, total_turn_duration_ms).EngineeringNo warnings★ 1.1K↓ —
- weekly-reporthoangsonww/Claude-Code-Agent-MonitorCompile a weekly productivity report using Agent Monitor data — daily_sessions and daily_events trends, per-session costs from pricing engine, token volumes (input/output/cache_read/cache_write + baselines), tool usage top 20, session completion rates by status, and workflow intelligence metrics.ProductivityNo warnings★ 1.1K↓ —
- budget-sethoangsonww/Claude-Code-Agent-MonitorDefine a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the Agent Monitor dashboard. Reads current spend from /api/pricing/cost to size the budget sensibly and explains every rule field before writing. Use when setting a spend limit or wiring up a budget guardrail.WritingNo warnings★ 1.1K↓ —
- hook-inventoryhoangsonww/Claude-Code-Agent-MonitorInventory hooks across the user, project, and project-local settings plus the ~/.claude/hooks scripts directory — read through the Agent Monitor Config Explorer API — and flag hooks that POST to the network or run arbitrary commands. Reads /api/cc-config/hooks and /api/cc-config/hook-scripts. Use when auditing hook safety.EngineeringNo warnings★ 1.1K↓ —
- fleet-runshoangsonww/Claude-Code-Agent-MonitorSummarize Workflow-tool fleet runs from the Agent Monitor — these fleets emit no hooks and are ingested from on-disk run journals. List recent runs with status and agents-per-run, then drill into a single run's per-agent detail. Reconciles against the live run-state endpoints. Use when reviewing Workflow() fleets rather than hook-instrumented interactive sessions.ProductivityNo warnings★ 1.1K↓ —
- event-tracehoangsonww/Claude-Code-Agent-MonitorTrace the full event chain for one Claude Code session into an ordered timeline of every event type with tool_name and summary, highlighting gaps, out-of-order events, and failures. Reads /api/events?session_id= and /api/sessions/:id from the Agent Monitor dashboard. Use when debugging what a session actually did, step by step.EngineeringNo warnings★ 1.1K↓ —
- data-exporthoangsonww/Claude-Code-Agent-MonitorExport Claude Code session and analytics data in JSON, CSV, or Markdown formats. Supports exporting sessions, events, costs, and analytics for external analysis or reporting. Use for data backup or integration.DataNo warnings★ 1.1K↓ —
- live-watchhoangsonww/Claude-Code-Agent-MonitorPolls the Agent Monitor /api/stats endpoint several times over a short window and reports the live deltas in active_sessions, active_agents, events_today, and ws_connections so you can see activity moving in real time. Use when watching the dashboard for live changes rather than a one-time snapshot.EngineeringNo warnings★ 1.1K↓ —
- cwd-rolluphoangsonww/Claude-Code-Agent-MonitorRoll up Claude Code sessions by working directory (project) from Agent Monitor data — session count, total cost, total tokens, and last-active timestamp per cwd — so per-project activity can be compared at a glance. Use when summarizing where effort and spend went across projects.EngineeringNo warnings★ 1.1K↓ —
- cost-reporthoangsonww/Claude-Code-Agent-MonitorProduce a scoped CCAM cost and token report by model, provider, source, and session. Use for spend reviews, model-mix analysis, unpriced usage detection, or export-friendly cost summaries.ProductivityNo warnings★ 1.1K↓ —
- model-mixhoangsonww/Claude-Code-Agent-MonitorBreak down Claude Code usage by model family (Opus / Sonnet / Haiku) from the Agent Monitor dashboard — each family's share of tokens, share of cost, and the spots where an expensive model is doing cheap work. Pulls per-model token and cost splits from /api/pricing/cost, current rates from /api/pricing, fleet token totals from /api/analytics, and per-session model assignment from /api/sessions. Use when deciding model routing or whether to downshift work to a cheaper tier.DataNo warnings★ 1.1K↓ —
- write-skillsdzhng/skillsCreate or revise agent skills. Use when adding a new skill file, renaming a skill, simplifying an existing skill, improving trigger descriptions, or deciding what belongs in a skill versus references, scripts, assets, or ordinary docs.WritingNo warnings★ 1.4K↓ —
- run-historyhoangsonww/Claude-Code-Agent-MonitorInspect CCAM dashboard-run history and relate live run handles to persisted Claude Code or Codex sessions. Use when finding a prior launched task, checking whether a run is still attached, reviewing start/end status, or deciding whether to resume, view, or relaunch work.EngineeringNo warnings★ 1.1K↓ —
- error-scanhoangsonww/Claude-Code-Agent-MonitorScan recent Claude Code activity for errors and failure signals across all sessions using Agent Monitor data — APIError events and PreToolUse→PostToolUse gaps (tools that started but never completed) — then group failures by tool and model and rank them by frequency. Use when checking for errors or asking "what's failing right now".EngineeringNo warnings★ 1.1K↓ —
- dag-maphoangsonww/Claude-Code-Agent-MonitorRender the multi-agent orchestration DAG for a session — parent→child subagent edges, tree depth, and fan-out — from the Agent Monitor workflow intelligence API. Cross-checks the orchestration dataset against the raw agent records and session detail. Use when visualizing how a session's agent structure was organized.MediaNo warnings★ 1.1K↓ —
- slo-checkhoangsonww/Claude-Code-Agent-MonitorDefine and check simple service-level objectives for Claude Code from Agent Monitor data — session completion rate, tool success rate (PostToolUse/PreToolUse), and error rate (APIError/total) — then compare each to its target and report the error budget remaining. Use when reporting reliability or when someone asks "are we meeting our SLOs?".EngineeringNo warnings★ 1.1K↓ —
- run-agenthoangsonww/Claude-Code-Agent-MonitorLaunch and supervise Claude Code or Codex through the CCAM Run API. Use when the user wants to start a monitored agent, select a model, approval policy, sandbox, or working directory, send a follow-up, inspect live output, resume a native session, or stop a dashboard-launched run.EngineeringNo warnings★ 1.1K↓ —
- i18n-parityhoangsonww/Claude-Code-Agent-MonitorMANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, full mirrored guides, locale-aware formatting, language switchers) in parity across every supported language. Use automatically (without being asked) whenever you add or change user-visible UI copy, add an i18n key, edit README-EN.md or a localized guide, edit wiki/index.html, or add a language surface.DesignNo warnings★ 1.1K↓ —Also in 1 other repo
- close-specdzhng/skillsWhen a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).PlanningNo warnings★ 1.4K↓ —
- landing-page-generatorkostja94/marketing-skillsDeprecated compatibility entry for Landing Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Landing Page.DesignNo warnings★ 1.1K↓ —
- display-adskostja94/marketing-skillsWhen the user wants to run display, banner, or ad network campaigns. Also use when the user mentions "display ads," "banner ads," "ad network," "ad alliance," "programmatic display," "native ads," or "retargeting display." For strategy, use paid-ads-strategy.MarketingNo warnings★ 1.1K↓ —
scheduler-and-booking-design
rampstackco/claude-skills
From the author
Designing meeting schedulers and booking experiences that qualify leads, set up calls well, and convert at higher rates than a generic Calendly link. Availability logic, qualification gating, prep automation, follow-up sequencing. Honest about any-time-friction (no qualification, just a booking link), interrogation-gate (so much qualification it scares users off), and qualified-fast-path (just enough qualification to set up the call well) patterns. Triggers on scheduler design, meeting booking, demo scheduling, sales call scheduling, calendar tool, booking page, qualification flow. Also triggers when sales team complains about cold demos, when booking conversion is poor, or when scheduler is being scoped for the first time.
Install
npx skills add rampstackco/claude-skills --skill scheduler-and-booking-design -a claude-code
Installs to .claude/skills/scheduler-and-booking-design/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
What it can touch
Safety checks on SKILL.md
No warnings.
Why 88
Files (11)
- README.md
- SKILL.md
- references/availability-logic-patterns.md
- references/common-scheduler-failures.md
- references/prep-automation-patterns.md
- references/qualification-field-design.md
- references/reminder-sequence-patterns.md
- references/reschedule-and-no-show-handling.md
- references/routing-patterns.md
- references/scheduler-anti-patterns.md
- references/scheduler-decision-criteria.md