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,415 skills from 2,407 repositories · updated 1 hour ago
49,413 skills
- 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↓ —
- 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↓ —
- icalp-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICALP (EATCS) campaign backward from its single annual February deadline, through abstract registration, the anonymous submission, the Track B rebuttal window, the April notification, and the LIPIcs camera-ready and presentation, and when coordinating a full-version (arXiv/ECCC) release alongside the anonymous submission.ProductivityNo warnings★ 1.4K↓ —
- focs-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when running the final pre-upload audit of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — the April HotCRP deadline clock, the abstract-references-plus-ten-pages attention rule, the 11-point single-column format floor, PDF security restrictions, double-blind checks, and SIGACT publication-policy compliance.SecurityNo warnings★ 1.4K↓ —
- regression-alerthoangsonww/Claude-Code-Agent-MonitorCompare this period's reliability against the prior period using Agent Monitor data — error rate (APIError/total) and tool-failure rate (PreToolUse→PostToolUse gap) — flag any regression where reliability got worse, and optionally wire a persistent alert rule so the dashboard catches the next regression automatically. Use when checking whether reliability degraded.OtherNo warnings★ 1.1K↓ —
- hook-diagnosticshoangsonww/Claude-Code-Agent-MonitorDiagnose Claude Code hook installation, delivery, and ingestion issues. Checks hook configuration, connectivity, event flow, and identifies common problems. Use when events are not appearing in the dashboard.EngineeringNo warnings★ 1.1K↓ —
- regression-watchhoangsonww/Claude-Code-Agent-MonitorDetect quality and efficiency regressions over time using Agent Monitor data — rising error rate (APIError events), falling cache hit rate, growing compaction frequency, and climbing cost-per-session. Splits history into an earlier baseline window and a recent window and reports which metrics are getting worse, by how much, and where. Use when checking whether things are degrading or trending in the wrong direction.OtherNo warnings★ 1.1K↓ —
- doca-upgradeNVIDIA/skillsChanging DOCA versions safely: upgrading or downgrading the host DOCA packages, refreshing the BlueField BFB, bumping the NGC DOCA container tag, or rolling back, with the discipline detect -> report -> ASK -> only then a guided upgrade. Trigger on "is there a newer DOCA", "I want the newest DOCA features, can I just apt upgrade in place", "should I move to the next release", "the upgrade stopped midway and dpkg is in a broken state", "my component is being deprecated, what now", or "roll me back", even without the word upgrade. Detect what is installed, find the newer release, report the gap, then STOP and ask for explicit confirmation; never upgrade automatically. Do not use it for a runtime error on an unchanged install (doca-debug). Version detection alone belongs to doca-version, first-time install to doca-setup, any hardware / firmware / reboot step to doca-hardware-safety, and public-docs or sunset routing to doca-public-knowledge-map.EngineeringNo warnings★ 3.9K↓ —
- plan-campaigngooseworks-ai/goose-skillsCampaign planner: turns a product, offer, goal, budget and date into a plan the marketer can approve and a designer can start from today, with every channel kept or dropped for a reason. Zero paid is a valid answer; it never spends. Use when the ask names a campaign, a launch, drop or season push, a budget or a date: I have this budget and a launch date — what do I run, where?; plan my launch, drop or Black Friday push; plan a campaign; how should I split $5k; plan next month's campaign; our CAC blew up — replan. Not for a broad "grow my brand", "get more customers" or "where do I start" with no campaign, budget or date — use where-to-start; not for pausing ads on a sold-out product — use run-paid-campaigns; not for an email-only send plan — use email-lifecycle; not for reading this week's numbers — use analyze-performance.MarketingNo warnings★ 1.3K↓ —
- session-timelinehoangsonww/Claude-Code-Agent-MonitorRender an ordered timeline of one Claude Code session's events (every event type) with per-event durations and tool names, reconstructed from Agent Monitor data. Pairs PreToolUse with PostToolUse to compute tool durations and surfaces gaps, errors, and compaction points. Use when reconstructing what happened in a session step by step.MediaNo warnings★ 1.1K↓ —
- brooks-sweepUpdatedhyhmrright/brooks-lintFull-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user wants to "fix everything", "sweep the codebase", "auto-fix all issues", "clean up the whole project", or asks for a single command that both diagnoses and remediates quality problems. Do NOT trigger for: read-only audits or health reports where the user only wants findings without code changes; single-dimension reviews (use the focused skill instead: brooks-review / brooks-audit / brooks-debt / brooks-test); server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime.TestingNo warnings★ 1.6K↓ —
- api-error-reporthoangsonww/Claude-Code-Agent-MonitorProduce a detailed report on APIError events from Agent Monitor data — counts over time, which sessions and models are affected, and the likely root cause (rate limits, overload/529, or context-window pressure) inferred from each event's summary and data payload. Use when API errors spike or when you need to explain why requests are failing.EngineeringNo warnings★ 1.1K↓ —
- session-comparehoangsonww/Claude-Code-Agent-MonitorCompare two sessions side-by-side using Agent Monitor data — per-model token usage (input/output/cache_read/cache_write + compaction baselines), pricing engine cost breakdowns, workflow intelligence (complexity scores, tool flow transitions, subagent effectiveness), session metadata (thinking_blocks, turn_count, turn_duration_ms, usage_extras), and full event timelines with all 10+ event types.ProductivityNo warnings★ 1.1K↓ —
- config-explorerhoangsonww/Claude-Code-Agent-MonitorInspect and safely edit the Claude Code and Codex configuration surfaces exposed by CCAM. Use when auditing skills, agents, commands, plugins, marketplaces, MCP servers, hooks, settings, memory, keybindings, profiles, rules, or instruction files, and when a backup-backed allowlisted edit is required.WritingNo warnings★ 1.1K↓ —
- brooks-healthUpdatedhyhmrright/brooks-lintCombined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic engineering books. Triggers when: user wants an overall quality assessment, asks "how healthy is this codebase?", "run all the checks", "I need a health score before the release", or wants to onboard a new team with a quality overview. Do NOT trigger for: server health checks, HTTP health endpoints, Kubernetes liveness/readiness probes, database health, or application uptime. Also do not trigger when the user specifically requests only one dimension — use the corresponding focused skill instead (brooks-review / brooks-audit / brooks-debt / brooks-test).TestingNo warnings★ 1.6K↓ —
- uai-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when converting an accepted UAI paper into its PMLR proceedings version, covering de-anonymization, final formatting against the UAI template, metadata for the PMLR volume, restoring public code and data links, poster and spotlight preparation for the conference, and sequencing work back from the camera-ready deadline.ScienceNo warnings★ 1.4K↓ —
- metric-designagentscope-ai/OpenJudgeUse when the user has evaluation principles or a dataset but needs help choosing the right graders, designing evaluation metrics, creating LLM-as-judge prompts, combining multiple metrics into a composite score, or building an automated evaluation pipeline. Also use when the user mentions grader selection, metric design, judge prompt engineering, rubric design, evaluation pipeline code, or "how to evaluate [X] automatically." Outputs executable OpenJudge pipeline code.DesignNo warnings★ 1.1K↓ —
- transcript-grephoangsonww/Claude-Code-Agent-MonitorSearch a Claude Code session transcript for a string or regex pattern and show every matching message with surrounding context. Reads /api/sessions/:id/transcript and resolves sessions via /api/sessions?limit= from the Agent Monitor dashboard. Use when hunting for a specific message, prompt, tool call, or error inside a session's conversation.PlanningNo warnings★ 1.1K↓ —
- time-of-dayhoangsonww/Claude-Code-Agent-MonitorDiscover when you are most active and most productive with Claude Code by bucketing sessions and events into hour-of-day and day-of-week bins from their timestamps, then flagging peak versus low-output windows. Uses the session list, per-session events, and analytics daily trends. Use when planning a schedule or deciding when to do deep work versus lighter tasks.DataNo warnings★ 1.1K↓ —
- minutes-x1-closeoutsilverstein/minutesPrepare a sourced Minutes meeting outcome for human-governed closeout of existing X1 work. Use when the user wants a meeting decision or commitment to close, defer, escalate, or retire a specific X1 coordination thread. Never use it to infer settlement, move money, contact anyone, or close X1 work automatically.PlanningNo warnings★ 1.6K↓ —Also in 1 other repo
- verification-before-completionGanyuanRan/AegisUse when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish, or hand off.EngineeringNo warnings★ 1.4K↓ —
- establishing-project-contextGanyuanRan/AegisUse when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.ProductivityNo warnings★ 1.4K↓ —
- pattern-detecthoangsonww/Claude-Code-Agent-MonitorDetect recurring patterns using the Agent Monitor's workflow intelligence — toolFlow transitions (tool A → B frequency matrices), recurring workflow patterns, agent co-occurrence pairs, model delegation habits, error propagation paths by agent depth, and compaction triggers. Use to discover habitual usage patterns and anti-patterns.ProductivityNo warnings★ 1.1K↓ —
- cost-breakdownhoangsonww/Claude-Code-Agent-MonitorBreak down Claude Code costs using the Agent Monitor pricing engine. Shows per-model costs (input, output, cache_read, cache_write at $/Mtok rates), per-session costs, daily trends, and compaction baseline token recovery. Use when analyzing spending, comparing model costs, or planning budgets.PlanningNo warnings★ 1.1K↓ —
regex-builder
mohitagw15856/pm-claude-skills
TestingUpdated 10 hours ago
From the author
Build a regular expression from a plain-English description, or explain an existing one. Use when asked to write a regex, match/validate/extract a pattern, or understand what a regex does. Produces the regex, a token-by-token breakdown, passing and failing test cases, and notes on flavor/edge cases.
Install
npx skills add mohitagw15856/pm-claude-skills --skill regex-builder -a claude-code
Installs to .claude/skills/regex-builder/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
What it can touch
Instructions onlyNo network use seenLicence: MIT
Safety checks on SKILL.md
No warnings.
Why 88
Security100
Provenance78
Maintenance100
Licence100
Adoption51
Files (1)
- SKILL.md