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,409 skills from 2,375 repositories · updated 3 hours ago
48,362 skills
- work-with-creators-creator-vettinggooseworks-ai/goose-skillsVets creators you have already named from their public pages. Covers the median views of their last 12 to 20 posts (sponsored and organic apart), a read of their comments, how often they post, audience fit with how sure it is, about 12 months of brand-safety checks, rival partnerships and rules for regulated categories. Gives a verdict with dated numbers for each one. Use alone when you already have the creator handles and the brand's goal; otherwise run work-with-creators.LegalNo warnings★ 1.3K↓ —
- marketing-data-accessgooseworks-ai/goose-skillsHow to get live public data (ads libraries, social posts and comments, search results, creator profiles), business identity/work-contact reads, domain SEO metrics and paid media generation through GooseWorks, with no vendor key. Load before any playbook step that reads public data or calls an outside model: which proxy call fits the job, what it costs, how to get the human's yes, and what to do when the data is not reachable. Not for brand facts (read the brand brain) or the customer's own ad accounts (the GooseWorks ads tools, or an ads connector they have).MarketingNo warnings★ 1.3K↓ —
- weekly-checkinhuytieu/COG-second-brainCross-domain pattern analysis and strategic reflection for weekly reviewEngineeringNo warnings★ 1.3K↓ —Also in 1 other repo
- nejm-fitbrycewang-stanford/Awesome-Journal-SkillsUse this first, before any writing, to stress-test whether a clinical study clears NEJM's bar — practice-changing clinical impact, methodological rigor, and generalizability. Decides NEJM vs Lancet/JAMA vs a specialty journal.TestingNo warnings★ 1.4K↓ —
- pnas-fitbrycewang-stanford/Awesome-Journal-SkillsUse before any writing begins to stress-test whether a result clears PNAS's bar — high quality and broad significance to a general scientific readership — and to make the realistic call between PNAS, Science/Nature, and a specialist field journal.TestingNo warnings★ 1.4K↓ —
- huggingface-tool-builderhuggingface/skillsUse this skill when the user wants to build tool/scripts or achieve a task where using data from the Hugging Face API would help. This is especially useful when chaining or combining API calls or the task will be repeated/automated. This Skill creates a reusable script to fetch, enrich or process data.OfficialEngineeringNo warnings★ 11.3K↓ —
- minutes-debriefsilverstein/minutesPost-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.OtherNo warnings★ 1.6K↓ —Also in 1 other repo
- research-market-market-passgooseworks-ai/goose-skillsStep of the research-market playbook: the worker brief for researching the market itself, including category, size, changes, pricing norms and demand. Run research-market instead; not for direct use.ScienceNo warnings★ 1.3K↓ —
- colt-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a COLT (Conference on Learning Theory) submission calendar backward from the single AoE paper deadline — proof-completion and verification milestones, writing and appendix-assembly passes, CMT logistics, the rebuttal window, decision aftermath, and PMLR camera-ready with conference presentation in early summer.ProductivityNo warnings★ 1.4K↓ —
- corl-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a CoRL submission cycle end to end — the late-May abstract and paper deadlines, the summer review window, first-round rejection risk, the August one-page rebuttal and discussion period, autumn decisions, the October PMLR camera-ready, and the November conference — including what to do between milestones.ProductivityNo warnings★ 1.4K↓ —
- colm-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a COLM submission campaign across the calendar — working backward from the late-March abstract and paper deadlines through the May-June rebuttal, July decisions, August camera-ready, and October conference, coordinating co-authors, compute, and reciprocal-reviewing duties, and slotting COLM into a multi-venue LM-research pipeline.ProductivityNo warnings★ 1.4K↓ —
- cikm-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a CIKM project calendar across the May abstract/paper gates, June short-track gates, August notification and camera-ready, and the November conference, including the post-submission phase now live in the 2026 cycle, multi-track coordination, and fallback planning toward CIKM 2027 or sibling venues.ProductivityNo warnings★ 1.4K↓ —
- cell-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when deciding which cell-* sub-skill to invoke next, or when sequencing a manuscript from significance test through reviewer rebuttal for Cell (Cell Press). Routes — it does not replace — the specialized skills.ProductivityNo warnings★ 1.4K↓ —
- chi-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ACM CHI Papers submission for PCS readiness, covering the September full-paper deadline, the anonymized single-column template, word-count norms instead of page limits, subcommittee designation, supplementary and video upload, anonymization of external links, and CHI's desk-reject triage before upload.MediaNo warnings★ 1.4K↓ —
- eacl-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an EACL project timeline through ACL Rolling Review, covering the single viable ARR cycle with no fallback, backward planning from the one deadline, the rebuttal window, the commitment decision to EACL, notification, and camera-ready through ACL Anthology publication, plus re-routing since the next chance is another conference.ProductivityNo warnings★ 1.4K↓ —
- fse-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ESEC/FSE research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the ACM Primary Article Template page budget, double-anonymous "heavy" anonymity, the open-science Data Availability statement, PACMSE publication, and desk-reject triage before the AoE cutoff.ScienceNo warnings★ 1.4K↓ —
- ecai-workflowbrycewang-stanford/Awesome-Journal-SkillsUse to plan an ECAI campaign end to end — run the single-round year backward from the paper deadline through the abstract/registration step, summary-reject phase, rebuttal window, notification, and the open-access camera-ready, adapting to whether the edition is a standalone ECAI (FAIA/PAIS) or the joint IJCAI-ECAI 2026.ProductivityNo warnings★ 1.4K↓ —
- edbt-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle, backward-planning through the author-feedback phase and the in-cycle revise-and-resubmit window, and handling the cycle-to-conference roll — for a database-systems paper published open access on OpenProceedings.ProductivityNo warnings★ 1.4K↓ —
- incident-responserampstackco/claude-skillsManage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers on incident response, production incident, outage, service down, site down, P0, P1, severity, downtime, on-call, incident commander, status page, postmortem prep. Also triggers when something is actively broken in production and the user is figuring out what to do.SecurityNo warnings★ 1K↓ —
- eccv-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when running an ECCV campaign end to end — the even-year calendar from February registration to the September conference, the retargeting triangle to CVPR and ICCV seen from the ECCV seat, where the 2026 cycle stands today, and backward planning a 2028 submission from the March deadline.ProductivityNo warnings★ 1.4K↓ —
- dac-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ACM/IEEE Design Automation Conference (DAC) Research-Manuscript submission for Softconf readiness, covering the two-stage abstract-then-manuscript deadline, the 6+1-page ACM double-column page budget with its references-only last page, the double-blind anonymization sweep, TPC conflict-of-interest declaration, and desk-reject triage before the mid-to-late-November cutoff.DesignNo warnings★ 1.4K↓ —
- iclr-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICLR project timeline from topic selection through OpenReview submission, discussion, revision, decision, camera-ready, poster, video, and public artifact release. Use when sequencing milestones against the current cycle's OpenReview deadlines, budgeting time for the long public discussion phase, or assigning owners for anonymity audits and reviewer-verifiable evidence paths.ProductivityNo warnings★ 1.4K↓ —
- hri-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ACM/IEEE HRI full-paper submission for PCS readiness — the mandatory abstract-then-paper two-step deadline, choosing the correct one of the five tracks, the 8-page acmart anonymous format, the double-blind sweep across PDF and video, the human-participants ethics acknowledgment, and desk-reject triage before the AoE cutoff.DocumentsNo warnings★ 1.4K↓ —
- hpca-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an HPCA project timeline from venue fit through the two-step July registration and paper gate, the autumn review wait, the single rebuttal/revision window, notification, IEEE camera-ready, artifact evaluation, and the February/March talk, with backward-planning offsets for a hardware-evaluated paper.ProductivityNo warnings★ 1.4K↓ —
cost-breakdown
hoangsonww/Claude-Code-Agent-Monitor
PlanningUpdated 23 hours ago
From the author
Break 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.
Install
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill cost-breakdown -a claude-code
Installs to .claude/skills/cost-breakdown/ · 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
Provenance77
Maintenance100
Licence100
Adoption49
Files (2)
- SKILL.md
- agents/openai.yaml