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 14 hours ago
48,055 skills
- openspec-exploreMemeMeow-Studio/MemeMeowEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.FinanceNo warnings★ 1.3K↓ —Also in 1 other repo
- openspec-apply-changeMemeMeow-Studio/MemeMeowImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.ProductivityNo warnings★ 1.3K↓ —Also in 1 other repo
- asc-submission-healthrorkai/app-store-connect-cli-skillsDiagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and retried. For staging, upload, publication, and submission execution, use asc-release-flow.EngineeringNo warnings★ 1.1K↓ —
- http-api-cloudbaseTencentCloudBase/CloudBase-AI-ToolkitCloudBase official HTTP API client guide. This skill should be used when backends, scripts, or non-SDK clients must call CloudBase platform APIs over raw HTTP instead of using a platform SDK or MCP management tool.EngineeringNo warnings★ 1.2K↓ —Also in 4 other repos
- openmeld-cliamplifthq/openmeldOfficial public OpenMeld Skill for agents using the `openmeld` CLI to consult the Center Agent, set up OpenMeld, connect local agents, create or request Agent Profiles, work in Organizations and Spaces, observe or stop Wakes, trace delivery, and repair local state.EngineeringNo warnings★ 1.4K↓ —
- operating-livekit-agentsfcakyon/claude-codex-settingsDeploys and operates a LiveKit agent in production: shipping a version to LiveKit Cloud and rolling it back, secrets and configuration, the worker process model and prewarming, safe async inside worker processes, provider timeouts and degradation, graceful shutdown, SDK upgrades, and observability. Use when the user says "deploy my agent", "roll back the deployment", "tail the agent logs", "the first call after a restart is slow", "attached to a different loop / event loop is closed", "prewarm the VAD", "shut down without dropping calls", "upgrade livekit-agents safely", "correlate logs by session", or is changing an agent codebase that is already live. Not for designing the agent (building-livekit-agents) or reproducing one bad conversation locally (debugging-livekit-agents).DevOpsNo warnings★ 1.2K↓ —
- fizz-convertpashov/skillsConvert English-language properties in PROPERTIES.md (produced by the Fizz skill) into Solidity assertions inside the existing fuzz harness, then flip their checkboxes. Trigger on "fizz-convert", "convert properties", "implement properties from PROPERTIES.md", "convert PROPERTIES.md to Solidity".OtherNo warnings★ 1.3K↓ —
- workers-best-practicesfcakyon/claude-codex-settingsCloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.DevOpsNo warnings★ 1.2K↓ —
- colt-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when positioning a COLT (Conference on Learning Theory) submission against prior bounds and models — building the known-versus-new comparison across COLT/ALT lineage, STOC/FOCS, NeurIPS-and-ICML theory tracks, statistics journals, and arXiv concurrency, while respecting anonymity and the parallel-submission rules.ScienceNo warnings★ 1.4K↓ —
- colt-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when converting an accepted COLT (Conference on Learning Theory) paper into its PMLR proceedings version, covering de-anonymization, acknowledgements and funding restoration, appendix consolidation into the archival PDF, PMLR volume metadata and BibTeX hygiene, rebuttal-promised edits, and presentation logistics.DocumentsNo warnings★ 1.4K↓ —
- cikm-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when positioning a CIKM submission against three literatures at once — retrieval, mining, and knowledge management/databases — building the boundary-work paragraph, guarding against misattributing SIGIR/KDD/ICDM classics to CIKM, and handling preprints under the arXiv-declaration and dual-submission rules.ScienceNo warnings★ 1.4K↓ —
- colm-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when converting a COLM acceptance into the final paper — the August 7 camera-ready deadline in 2026, de-anonymization and the one-page acknowledgments allowance, folding rebuttal commitments into the text, publishing on OpenReview, releasing artifacts publicly, and planning the October conference in San Francisco.ScienceNo warnings★ 1.4K↓ —
- colm-related-workbrycewang-stanford/Awesome-Journal-SkillsUse when positioning a COLM paper inside the fastest-moving literature in ML — triaging arXiv-heavy citations, handling concurrent work fairly, citing model and dataset artifacts correctly, distinguishing COLM's three-edition archive from adjacent venues' archives, and keeping self-citation double-blind safe.ScienceNo warnings★ 1.4K↓ —
- cav-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising a CAV (Computer Aided Verification) paper for a precise verification contribution on the first page, an explicit soundness/completeness statement, theorem-and-proof discipline in the LNCS page budget, fair benchmark claims, honest scope and limits, and double-blind wording for the anonymized categories.WritingNo warnings★ 1.4K↓ —
- cikm-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical program of a CIKM paper — matching evidence to the claim's lanes across retrieval, mining, and knowledge-management evaluation cultures, choosing datasets and baselines that survive a blended panel, isolating the boundary mechanism, and meeting applied-track deployment-evidence bars.DevOpsNo warnings★ 1.4K↓ —
- colt-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when deciding whether a COLT (Conference on Learning Theory) paper needs numerical content at all — COLT has no experiments requirement — and, when numerics genuinely help, designing small illustrative simulations that visualize a proved bound, a separation, or a phase transition without diluting the theory.MediaNo warnings★ 1.4K↓ —
- chi-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when drafting or revising the prose of an ACM CHI paper — contribution statements, structure for mixed reviewer audiences, participant voice, calibrated claims, accessible and bias-free writing, and length discipline in a venue that reviews words against contribution instead of pages.WritingNo warnings★ 1.4K↓ —
- colm-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical core of a COLM paper — contamination analysis for evaluation data, fair baselines under matched prompting and compute, pinned model versions and decoding parameters, uncertainty over runs and samples, scaling coverage, and honest reporting of API-model comparisons.ScienceNo warnings★ 1.4K↓ —
- research-competitorsgooseworks-ai/goose-skillsCompetitor research: what every main rival is running, launching, charging and saying now, what works for them, and what that means for you. Use when the marketer asks for competitor research or a teardown, "what ads are my competitors running", "how do they price", "find gaps and angles", "what changed this week" (a weekly watch), or "X just launched / shut down / cut prices" (react now). Also builds a sales battlecard, checks a competitor page's tools/pixels, or studies who engages with their LinkedIn posts. Delivers a readable report saved to the brand, so the next run reports what changed. Never copies their words or disparages them. Not for what people say about you or your market — use research-market; not for who your buyers are — use research-audience.ScienceNo warnings★ 1.3K↓ —
- research-competitors-category-passgooseworks-ai/goose-skillsStep of the research-competitors playbook: the worker brief covering the whole category, including searches, AI answers, community threads and category ad winners. Run research-competitors instead; not for direct use.ScienceNo warnings★ 1.3K↓ —
- reviewdzhng/skillsCloseout pass on a finished substantive change — sequence refactor-clean (shape), code-review (diff), and write-docs (docs) so all three run, in the order where each feeds the next. Use after implementing a slice or feature and before calling it done or committing; when the user asks for a final review, a cleanup-and-document pass, or to "review everything." For a diff-only audit, reach code-review directly.EngineeringNo warnings★ 1.4K↓ —
- acl-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when revising an ACL paper for computational-linguistics house style, covering task-first framing, linguistic examples tied to quantitative error analysis, scoping language claims to tested languages, LLM-era claim discipline, anonymous self-reference, Limitations prose, and compressing into the 8-page or 4-page ACL format.WritingNo warnings★ 1.4K↓ —
- acl-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when organizing appendices and supplementary material for an ACL paper under ACL Rolling Review, covering the mandatory Limitations and optional ethics sections, appendices after references, anonymized software and data archives, the no-cloud-links rule, and deciding what must stay in the 8-page or 4-page body.ScienceNo warnings★ 1.4K↓ —
- ase-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when deciding what belongs in the 10-page ASE (IEEE/ACM Automated Software Engineering) paper body versus the artifact and supplementary material, splitting content by decision-criticality so nothing that decides acceptance lives outside the reviewed pages under the 10+2 budget.ScienceNo warnings★ 1.4K↓ —
jtbd-framing
rampstackco/claude-skills
OtherUpdated Oct 27, 2026
From the author
The Jobs-to-be-Done framework as applied product methodology. Job statements, struggling moments, hire and fire criteria, the difference between feature-thinking and job-thinking. Honest about where JTBD adds clarity (discovery, prioritization, positioning) and where it becomes performative ritual (job-statement workshops that do not drive decisions, persona-theater disguised as JTBD). Triggers on jobs-to-be-done, JTBD, job statements, struggling moments, hire criteria, fire criteria, switch triggers, functional emotional social jobs, outcome-driven innovation. Also triggers when a team is over-relying on feature-request lists or persona archetypes that do not drive product decisions, when a positioning conversation needs the framing JTBD provides, or when discovery is producing outputs that do not connect to product strategy.
Install
npx skills add rampstackco/claude-skills --skill jtbd-framing -a claude-code
Installs to .claude/skills/jtbd-framing/ · 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
Provenance76
Maintenance100
Licence100
Adoption49
Files (10)
- README.md
- SKILL.md
- references/applying-jtbd-to-discovery.md
- references/applying-jtbd-to-positioning.md
- references/applying-jtbd-to-prioritization.md
- references/common-jtbd-failures.md
- references/functional-emotional-social-dimensions.md
- references/hire-and-fire-criteria.md
- references/identifying-struggling-moments.md
- references/job-statement-structure-patterns.md