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,105 skills from 2,358 repositories · updated 17 hours ago
48,055 skills
- 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↓ —
- push-to-forked-prhoangsonww/Claude-Code-Agent-MonitorPush the current working tree directly to a GitHub PR whose head lives on a **fork**, without creating a new branch and without pushing to `origin` (which is usually the upstream). Invoke when the user says things like "push straight to PROtherNo warnings★ 1.1K↓ —Also in 2 other repos
- 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↓ —
- oversized-skillfirst-fluke/oh-my-agentA skill whose body deliberately exceeds the 500-line recommendation.OtherNo warnings★ 1.4K↓ —
- brooks-sweephyhmrright/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↓ —
- 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↓ —
- 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-recordsilverstein/minutesStart or stop recording a meeting, call, or voice memo. Use this whenever the user says "record", "start recording", "capture this meeting", "stop recording", "I'm in a meeting", "take notes on this call", or wants to transcribe live audio. Also use when they ask about recording status or want to know if something is being recorded.MediaNo warnings★ 1.6K↓ —Also in 1 other repo
- code-explainermohitagw15856/pm-claude-skillsExplain what a piece of code does in plain English, at the depth the reader needs. Use when asked to explain code, walk through a function, understand an unfamiliar snippet, or onboard to a file. Produces a one-line summary, a step-by-step walkthrough, the non-obvious parts called out, and any bugs or smells spotted along the way.EngineeringNo warnings★ 1.5K↓ —
- cn-shuzhi-deckmohitagw15856/pm-claude-skillsUse when asked 帮我做述职 PPT, 述职 PPT 大纲, 年终述职怎么讲, 10 分钟述职讲稿, 述职 PPT 每页写什么, or turn a written year-end review into a 述职 presentation. Produces a slide-by-slide 述职 PPT outline with a conclusion-first headline per slide (结论先行), the chart or visual for each, a timed speaking script (讲稿) that fits the slot, a one-slide version for a short slot, and a rehearsal and Q&A checklist. For writing the review itself use cn-year-end-review; for a promotion to the next level use cn-promotion-defence.DocumentsNo warnings★ 1.5K↓ —
- asc-app-create-uirorkai/app-store-connect-cli-skillsCreate a new App Store Connect app record via browser automation. Use when there is no public API for app creation and you need an agent to drive the New App form.DesignNo warnings★ 1.1K↓ —
- the-strong-nomohitagw15856/pm-claude-skillsFind the real reason to NOT do the exciting thing you're about to commit to — the honest case against, before the excitement carries you in. Use when asked talk me out of this, should I really do this, what's the case against, or I'm excited but is this a mistake. Produces the strongest honest argument for not doing it, the excitement biases clouding your judgment, the specific conditions under which this is a bad idea for you, and a clear read on whether the strong no actually wins — protecting you from the plans that feel great and end badly.PlanningNo warnings★ 1.5K↓ —
- decision-panelmohitagw15856/pm-claude-skillsRun a decision past a panel of clashing advisors — an optimist, a pessimist, a numbers person, an ethicist, and future-you — then get a chair's verdict. Use when asked to help me decide, weigh this decision, what should I do about, or run this by different advisors. Produces each advisor's honest take on the decision (each committed to their lens), where they disagree most, the question that would break the tie, and a chair's recommendation that weighs the panel — turning a lonely choice into a structured board meeting.OtherNo warnings★ 1.5K↓ —
- ipsn-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing IPSN-lineage evaluations, covering real testbeds and deployments, ground-truth instrumentation, energy/latency/footprint measurement on real hardware, on-device/TinyML profiling, estimation-theoretic baselines and bounds, and matching evidence to the shape of each sensing claim across the IP and SPOTS tracks.DevOpsNo warnings★ 1.4K↓ —
- lancet-writingbrycewang-stanford/Awesome-Journal-SkillsUse to structure and hold the length of a Lancet Article main text — Introduction, Methods, Results, Discussion (~3000–3500 words), the Research in context panel, a limited reference list (~30), and a cautious, globally minded Discussion that does not overstate.WritingNo warnings★ 1.4K↓ —
- imc-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when drafting or revising the prose of an ACM IMC measurement paper, covering the first-page measurement finding, making vantage points and methodology auditable, longitudinal framing for a moving Internet, arguing limitations rather than reciting them, writing the Ethics section early, and acmart page-budget discipline.WritingNo warnings★ 1.4K↓ —
- icse-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an ICSE research-track paper, covering subject and benchmark selection, baseline fairness, statistical tests and effect sizes as SE reviewers expect them, qualitative-methods rigor, ablations for AI-based techniques, and threats-driven study design.TestingNo warnings★ 1.4K↓ —
- icdm-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical evaluation for an ICDM (IEEE International Conference on Data Mining) paper - mining-task definition, strong and fairly-tuned baselines, ablations that isolate the named mechanism, scalability curves that test scale claims, and discovery-validity checks that separate real findings from evaluation artifacts.TestingNo warnings★ 1.4K↓ —
- icra-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the experimental section of an ICRA paper — real-robot versus simulation-only evidence, trial counts and success-rate reporting, task distributions and resets, baseline fairness on shared hardware, sim-to-real transfer claims, failure-mode analysis, and the statistics robotics reviewers actually expect.ScienceNo warnings★ 1.4K↓ —
- focs-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when deciding whether and how computation appears in a FOCS (IEEE Symposium on Foundations of Computer Science) paper — a venue that accepts on theorems with no evaluation section expected — covering machine-verified case analyses, computer-discovered constructions, and honest illustrative plots.MediaNo warnings★ 1.4K↓ —
- hri-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when planning the supplementary materials for an ACM/IEEE HRI full paper — above all the video figure that shows the embodied interaction, plus study instruments, extended results, and appendices — deciding what a reviewer must see to judge the interaction versus what belongs outside the 8-page body, all anonymized for double-blind review.MediaNo warnings★ 1.4K↓ —
- fse-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when deciding what belongs in an ESEC/FSE paper body versus its anonymized artifact and appendices, covering the ACM-template page budget, the rule that decision-critical evidence stays inside the reviewed pages, double-anonymous supplementary material, and how to split an empirical-SE paper between body and package.ScienceNo warnings★ 1.4K↓ —
- telemetrymicrosoft/power-platform-skillsUse this skill when the user wants to enable, disable, turn on or off, opt out of, opt in to, or check the status of power-automate telemetry / usage data. Triggers: "disable telemetry", "turn off telemetry", "opt out of telemetry", "stop collecting usage data", "enable telemetry", "telemetry status".OtherNo warnings★ 1.1K↓ —
- cvpr-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the experimental program of a CVPR paper, covering benchmark and baseline selection under matched-compute fairness, the ablation study reviewers treat as mandatory, qualitative and failure-case evidence, efficiency metrics tied to the Compute Reporting Form, and generalization tests beyond a single dataset.TestingNo warnings★ 1.4K↓ —
claims-triage
mohitagw15856/pm-claude-skills
EngineeringUpdated 23 hours ago
From the author
Triage an incoming insurance claim: check the coverage trigger against policy wording, band severity and complexity, screen for fraud indicators, set a first-pass reserve range, and route with an SLA. Use when asked to triage a claim, review a first notice of loss (FNOL), assess a new claim, decide fast-track vs adjuster routing, or screen a claim for SIU referral. Produces a structured triage note with coverage view, severity band, indicator screen, reserve range, and a routing recommendation.
Install
npx skills add mohitagw15856/pm-claude-skills --skill claims-triage -a claude-code
Installs to .claude/skills/claims-triage/ · 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