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,399 skills from 2,375 repositories · updated 44 minutes ago
48,352 skills
- torchdrugK-Dense-AI/scientific-agent-skillsBuilds and troubleshoots TorchDrug 0.2.1 workflows for molecular graphs, property prediction, self-supervised pretraining, molecule generation, retrosynthesis, protein representation learning, and knowledge graph reasoning. Use when code imports torchdrug or needs its datasets, models, tasks, or Engine.ScienceNo warnings★ 56K↓ —Also in 1 other repo
- fluidsimK-Dense-AI/scientific-agent-skillsPlans, configures, inspects, restarts, and analyzes bounded FluidSim computational-fluid-dynamics simulations with explicit numerical-validity and HPC safety checks. Use for FluidSim solver selection, parameter review, FFT/MPI setup, output diagnostics, or restart compatibility.PlanningNo warnings★ 56K↓ —Also in 1 other repo
- hypogenicK-Dense-AI/scientific-agent-skillsPlans and audits use of ChicagoHAI HypoGeniC/HypoRefine for LLM-assisted hypothesis generation from labeled text datasets. Use for the `hypogenic` package, its task configs, hypothesis banks, or HypoBench datasets—not for manual hypothesis formulation or scientific validation.ScienceNo warnings★ 56K↓ —Also in 1 other repo
- chief-revenue-officercbrock84/headcountAn agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs in Claude Code and ChatGPT.LegalNo warnings★ 2.6K↓ —
- write-a-postmorteminkeep/open-knowledgeWrite a blameless incident postmortem under postmortems/ following the Google SRE shape — evidence-based timeline, trigger vs root cause vs symptom, contributing factors, what went well, and owned+dated+verifiable action items. Read when asked to write a postmortem, do an incident review, run a root cause analysis, write up the outage, retro on the outage, or when the user says we had an incident and wants it documented. Do NOT read to frame a proposal (use frame-a-proposal), write a spec (use write-a-spec), record a decision (use record-a-decision), or review a design (use review-a-design) — a postmortem documents an incident that already happened, it does not propose, specify, decide, or critique future work.WritingNo warnings★ 4.8K↓ —
- founder-opsJakeschincariol/founder-skillYour operations manager. Works out how the business actually runs on day one: suppliers and what they cost, who works when, the step-by-step routines for opening, serving or shipping and closing, the tools to run it, the licences and permits to check, and a risk register with what to do when each thing goes wrong. Feeds real costs back to the CFO. Use when the user says "how do I run this", "operations", "suppliers", "staffing", "SOPs", "what do I need to open", "permits", or "day one".OtherNo warnings★ 2.4K↓ —
- record-a-decisioninkeep/open-knowledgeRecords an architecture decision as a Nygard/MADR-shaped ADR under decisions/ — capturing the context that forced the choice, the options weighed, the decision itself, and its consequences in both directions, plus the supersedes chain that keeps a decision log honest. Read when asked to record an architecture decision, write an ADR, log the decision we made, document why we chose X over Y, capture this decision for the record, or supersede an old decision with a new one. Do NOT read to frame a proposal or explore an idea not yet decided (frame-a-proposal), to write a spec or implementation plan (write-a-spec), to write an incident postmortem (write-a-postmortem), or to judge whether a design is sound (review-a-design). This skill records a decision already made; it does not make one.DesignNo warnings★ 4.8K↓ —
- review-a-designinkeep/open-knowledgeReviews whether a design is SOUND — solving the right problem, derived from its stated goals and constraints — and emits ranked, evidence-backed findings, not edits. Read when asked to 'review this design', 'is this design sound', 'pressure-test this proposal', 'do a design review', 'does this solve the right problem', 'poke holes in this spec', 'should we build this', or to critique a proposal / spec / ADR / architecture or product decision. Do NOT read when the user wants to AUTHOR one of these — routing a new proposal is frame-a-proposal, a spec is write-a-spec, a decision record is record-a-decision, a postmortem is write-a-postmortem. Do NOT read for code review of a diff, or to fact-check individual claims (that is a correctness pass, a different job).DesignNo warnings★ 4.8K↓ —
- software-design-philosophywondelai/skillsManage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", "pass-through method", "this code is over-engineered", or "simplify this design". Also trigger when reviewing an interface for simplicity, evaluating whether an abstraction is pulling its weight, deciding whether a comment is worth writing, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For architecture boundaries, see clean-architecture.DesignNo warnings★ 2.6K↓ —Also in 2 other repos
- write-a-specinkeep/open-knowledgeScope a feature end to end and write an implementation spec under specs/ from an accepted proposal — current-system mapping, goals/non-goals, a Decision Log for one-way-door choices, a live Open Questions backlog, and a real migration + test plan. Read when asked to write a spec, scope this feature, turn this proposal into a spec, plan the implementation, or break this into tasks. Do NOT fire on frame a proposal or write the PRD (sibling frame-a-proposal — a PRD frames a change before it is accepted; this skill starts once one is), record a decision or write the ADR (record-a-decision), write a postmortem (write-a-postmortem), or review this design (review-a-design) — those are separate skills. Complements the platform open-knowledge skill; does not replace it.WritingNo warnings★ 4.8K↓ —
- consolidate-notesinkeep/open-knowledgePromote existing research into a stable-status canonical article under `articles/` in a Knowledge Base project (the `knowledge-base` starter pack). Read when a decision has actually been made and the team wants the source-of-truth written down, or when asked to consolidate, canonicalize, promote research, or supersede an older article. Carries the decision-confirmation gate, the `supersedes:` chain that keeps the evidence trail intact, and the canonical voice. Does not conduct new research — that is the sibling `research-with-sources` skill.ProductivityNo warnings★ 4.8K↓ —
- pentest-checklistzebbern/claude-code-guideThis skill should be used when the user asks to "plan a penetration test", "create a security assessment checklist", "prepare for penetration testing", "define pentest scope", "follow security testing best practices", or needs a structured methodology for penetration testing engagements.SecurityNo warnings★ 4.7K↓ —
- good-strategy-bad-strategywondelai/skillsFormulate and audit real strategy using Richard Rumelt's "Good Strategy Bad Strategy": an honest diagnosis, a guiding policy, and coherent action instead of goals, vision, and wishful thinking. Use when the user mentions "good strategy bad strategy", "strategy kernel", "diagnosis guiding policy coherent action", "our strategy is just goals", "strategic planning", "mission vs strategy", "annual plan", or "is this actually a strategy". Also trigger when auditing a strategy doc or pitch deck for fluff, turning a goal list into real strategy, formulating strategy for a product or company, or finding leverage and proximate objectives. Covers the kernel of strategy, bad-strategy detection, and sources of power. For product positioning, see obviously-awesome. For uncontested markets, see blue-ocean-strategy.DocumentsNo warnings★ 2.6K↓ —Also in 2 other repos
- software-lifecycleinkeep/open-knowledgeHow to work in a Software Lifecycle project (the `software-lifecycle` starter pack): proposals → decisions → specs → postmortems, plus guides. Read when the project has these folders, or when asked how this project is organized. Carries the doc lifecycle, status flows, and per-folder agent behaviors so that guidance does not live inside template bodies or folder descriptions. The five workflows — frame a proposal, write a spec, record a decision, write a postmortem, review a design — each ship as their own sibling skill in this pack. Complements the platform `open-knowledge` skill; does not replace it.DesignNo warnings★ 4.8K↓ —
- dsh-error-handlingNewqufei1993/skills-hub实现或审查错误传播、部分成功、结果未知、恢复、重试、取消或失败反馈时使用，明确状态保证和错误处理责任。OtherNo warnings★ 1.9K↓ —
- dsh-code-reviewNewqufei1993/skills-hub审查代码改动或 PR 时使用，依据目标项目的实际需求检查正确性、生命周期、接口行为、验证证据和文档，报告有依据且可采取行动的问题。EngineeringNo warnings★ 1.9K↓ —
- archify-tuningtt-a1i/archifyImprove Archify diagram accuracy, visual quality and complete authoring speed with fewer repairs. Use for generation experiments or evaluating changes to layout, routing, diagnostics, authoring instructions and acceptance rules against actual diagrams and agent traces.OtherNo warnings★ 93K↓ —
- architecture-optimizationwondelai/skillsGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says 'it works but it is slow and getting worse'. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.PlanningNo warnings★ 2.6K↓ —Also in 2 other repos
- kaltstart-triageKlotzkette/claude-fuer-deutsches-rechtFür Kaltstart Triage: routet Rolle, Frist, Unterlagen und Fachschritt; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: Arbeitsrecht.OtherNo warnings★ 1.8K↓ —
- leasing-agbKlotzkette/claude-fuer-deutsches-rechtFür Leasing AGB: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.OtherNo warnings★ 1.8K↓ —
- revclawLeoYeAI/agent-master-skillsSubmit and discover location-tagged reviews across the OpenClaw agent network. Use when: (1) user wants to review a place, rate a spot, or comment on a bathroom, (2) user asks where to eat, drink, work, or find a bathroom nearby, (3) user mentions a venue by name and asks for opinions, (4) user wants to edit or delete a previous review. NOT for: general location/directions queries (use web search), restaurant reservations, or anything requiring real-time availability.WritingNo warnings★ 2.2K↓ —
- writing-workflowinkeep/open-knowledgeHow to work in a Writing Pipeline project (the `writing-pipeline` starter pack): a three-stage drafting flow, ideas → drafts → published. Read when the project has these folders, OR when asked to capture an idea, start or revise a draft, review a piece before it ships, or publish it. Carries the stage flow and review behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.WritingNo warnings★ 4.8K↓ —
- codebase-wikiinkeep/open-knowledgeHow to work in a Codebase Wiki project (the `codebase-wiki` starter pack): an agent-authored, source-grounded wiki of the surrounding codebase. Read when the project has a `wiki/` knowledge base with `architecture/`, `modules/`, `flows/`, `concepts/`, and `guides/` sections plus `wiki/OVERVIEW.md`, or when asked to generate or refresh a wiki of this codebase. Carries the per-folder rules and freshness + log discipline, summarizes the audience/depth knobs and source-reference convention, and bundles the full generate/refresh procedure in `references/`. Complements the platform `open-knowledge` skill; does not replace it.PlanningNo warnings★ 4.8K↓ —
- energievertraegeKlotzkette/claude-fuer-deutsches-rechtFür Energie-Verträge — Strukturierung und Prüfung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.OtherNo warnings★ 1.8K↓ —
venue-templates
K-Dense-AI/scientific-agent-skills
DocumentsUpdated yesterday
From the author
Prepares journal manuscripts, conference papers, research posters, and grant documents using venue-specific formatting guidance and bundled LaTeX scaffolds. Supports selecting an official template, checking current page or anonymity rules, adapting academic writing to a venue, or inspecting a submission PDF.
Install
npx skills add K-Dense-AI/scientific-agent-skills --skill venue-templates -a claude-code
Installs to .claude/skills/venue-templates/ · 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
Runs bundled scriptsNo network use seenLicence: MIT
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 89
Security85
Provenance95
Maintenance100
Licence100
Adoption73
Files (32)
- SKILL.md
- assets/examples/cell_summary_example.md
- assets/examples/medical_structured_abstract.md
- assets/examples/nature_abstract_examples.md
- assets/examples/neurips_introduction_example.md
- assets/grants/nih_specific_aims.tex
- assets/grants/nsf_proposal_template.tex
- assets/journals/elsarticle-harv.bst
- assets/journals/elsarticle-num-names.bst
- assets/journals/elsarticle-num.bst
- assets/journals/elsarticle-template-harv.tex
- assets/journals/elsarticle-template-num-names.tex
- +20 more