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 2 hours ago
48,055 skills
- scrapecreators-apigooseworks-ai/goose-skillsProvider reference for collecting public profiles, posts, comments, transcripts, trends, and ad-library data from major social platforms through ScrapeCreators. Use as a dependency of research workflows, not as the final user-facing deliverable.BrowserNo warnings★ 1.3K↓ —
- asc-ppp-pricingrorkai/app-store-connect-cli-skillsSet territory-specific pricing for subscriptions and in-app purchases using current asc setup, pricing summary, price import, and price schedule commands. Use when adjusting prices by country or implementing localized PPP strategies.PlanningNo warnings★ 1.1K↓ —
- research-audience-signals-and-hooksgooseworks-ai/goose-skillsFor a list of companies, finds dated, linked timing signals from the last 90 days (funding, new leaders, hiring, launches), drops stale ones and noise, scores timing, and gives one personal hook per person from their recent public work. Facts only, no message copy. Use alone when you already have the company list and, for hooks, the people; otherwise run research-audience.ScienceNo warnings★ 1.3K↓ —
- brooks-harnesshyhmrright/brooks-lintMaintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .codex/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "do the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint tTestingNo warnings★ 1.6K↓ —
- asc-metadata-syncrorkai/app-store-connect-cli-skillsSync, validate, and apply App Store metadata and store assets with asc. Use when updating localizations, keywords, App Clip or preview assets, Asset Library media and placements, or migrating legacy fastlane metadata.OtherNo warnings★ 1.1K↓ —
- improve-search-visibility-citation-checkgooseworks-ai/goose-skillsStep of the improve-search-visibility playbook: runs the agreed buyer questions on AI and Google surfaces, records every run and scores how often the brand is named. Run improve-search-visibility instead; not for direct use.OtherNo warnings★ 1.3K↓ —
- oma-scmfirst-fluke/oh-my-agentManage Git branches, merges, conflicts, commits, and release baselines. Use for repository history and change-management operations.EngineeringNo warnings★ 1.4K↓ —
- oma-pmNewfirst-fluke/oh-my-agentTurn product requirements into scoped tasks with dependencies and acceptance criteria. Use for implementation planning and prioritization.PlanningNo warnings★ 1.4K↓ —
- new-skillhyhmrright/brooks-lintScaffold a new brooks-lint analysis skill so it passes `npm run validate` and `npm run evals` on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends paired eval scenarios. Triggers when the maintainer asks to "add a new skill", "scaffold a skill", or "create a brooks-lint mode". Do NOT trigger for: editing an existing skill's content, adding a single eval to an existing skill, or authoring skills for some other plugin.WritingNo warnings★ 1.6K↓ —
- research-marketgooseworks-ai/goose-skillsMarket research and brand watch: which market the brand is in, how big the reachable part is, what's changing, how buyers buy and what they pay, what people are saying now, and what it means for positioning. Use when the marketer asks for market research, "how big is my market", "what's changing in my category", "what do others charge", "what are people saying about us", "is there demand for <idea>", or "watch my brand / tell me if something blows up" (alerts only, risk first). Also writes positioning choices and finished messages ("position my product", "write our positioning"). Researches first, asks only decisions at the end, and saves the output to the brand. Not for who the buyers are and their own words — use research-audience; not for a deep look at rivals — use research-competitors.ScienceNo warnings★ 1.3K↓ —
- oma-skill-creationfirst-fluke/oh-my-agentCreate or revise OMA skills and their references. Use for skill routing, execution contracts, conditional loading, and authoring validation.OtherNo warnings★ 1.4K↓ —
- plan-campaign-channel-decisiongooseworks-ai/goose-skillsStep of the plan-campaign playbook: marks each candidate channel Run, Test, Later or No with a brand-fact reason and founder hours. Run plan-campaign instead; not for direct use.MarketingNo warnings★ 1.3K↓ —
- local-seokostja94/marketing-skillsWhen the user wants to optimize for local search, set up Google Business Profile, or build local citations. Also use when the user mentions "local SEO," "Google Business Profile," "Google Maps," "NAP," "citations," "local search," "local business," or "service area." For location pages, use programmatic-seo.MarketingNo warnings★ 1.1K↓ —
- oma-dbfirst-fluke/oh-my-agentDesign schemas and migrations, tune queries, or plan vector retrieval and database operations. Application API implementation uses oma-backend.DataNo warnings★ 1.4K↓ —
- brooks-debthyhmrright/brooks-lintTech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what should we fix first?", or "how do I justify refactoring to management?". Do NOT trigger for: server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime — "health" in those contexts is infrastructure, not code quality. Also not for single-function refactoring questions.DevOpsNo warnings★ 1.6K↓ —
- iso27701Sushegaad/Claude-Skills-Governance-Risk-and-ComplianceExpert ISO 27701 Privacy Information Management System (PIMS) compliance advisor. Use this skill whenever a user asks about ISO/IEC 27701:2025, ISO/IEC 27701:2019, privacy information management, PIMS certification, PII controller or processor obligations, privacy risk assessment, Statement of Applicability for privacy, privacy by design, data subject rights, DPIA, records of processing activities, transitioning from ISO 27701:2019, GDPR alignment with ISO 27701, or any privacy management system topic. Also trigger for questions about Annex A.1 (controller controls), A.2 (processor controls), A.3 (shared security controls), or implementing a standalone PIMS without ISO 27001. When in doubt, use this skill — it covers the full ISO 27701 lifecycle from gap assessment through certification.SecurityNo warnings★ 1K↓ —
- releasehyhmrright/brooks-lintCut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release", "cut a release", "ship a new version", or "bump and publish" brooks-lint. Do NOT trigger for: propagating an already-decided version without releasing (use `npm run bump` directly), CHANGELOG edits alone, or questions about the release process that don't ask to perform it.WritingNo warnings★ 1.6K↓ —
- oma-voiceUpdatedfirst-fluke/oh-my-agentGenerate or transcribe speech with Voicebox or VoiceStudio, or process existing audio locally. Use for narration, transcripts, timed speech, and loudness conversion; video editing uses oma-video.MediaNo warnings★ 1.4K↓ —
- investigate-processmicrosoft/power-platform-skillsUse when a broad Process Mining business question, observed pattern or competing explanation needs investigation across analytical perspectives.FinanceNo warnings★ 1.1K↓ —
- oma-imageUpdatedfirst-fluke/oh-my-agentGenerate raster images or reference-guided variations through the OMA image CLI. Use for image assets or explicit vendor comparisons; pixel editing uses an editor.MediaNo warnings★ 1.4K↓ —
- chi-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ACM CHI submission cycle end to end — the single September deadline, two-round review with a five-week revise-and-resubmit window, December decisions, the TAPS and publication-ready chain, and the May conference — with owners and risk buffers for each stage.ProductivityNo warnings★ 1.4K↓ —
- test-native-extensionmicrosoft/power-platform-skillsValidate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCT_EXPORT_METHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg constructor, iOS [cls new] no-arg init, requiresMainQueueSetup NO, non-throwing eager construction), so launch-time crashes surface before any build. Layer 2 validates the committed `./manifest.json` against the ppmplugin-format rules. Layer 3 asserts request/response/error-code agreement across native and PCF. Layer 4 compiles the PCF (auto-skipped if absent). Layer 5 prints a device end-to-end recipe. Native compile belongs to /build-android-binary and /build-ios-binary — this is the cheap structural pre-flight before those slow builds. Reports pass/fail per layer with a fix hint and updates .extension-state.md.TestingNo warnings★ 1.1K↓ —
- writing-relayflowsAgentWorkforce/relayUse when authoring a Relayflows flow (@relayflows/surface / @relayflows/sdk, the journal-based v2 engine — the CLI is `flows`, package versions 2.0.x) in TypeScript or YAML/JSON. Covers the three-rung ladder (run/llm/agent), the resident verbs (human/dispatch/done), verification gates, TypeScript vs YAML authoring, per-step cli/model selection and its resolution order, flows.json, and `flows check`/`run`/`resume` with their real refusal shapes and exit codes. Not for the older, unrelated `@relayflows/core` WorkflowBuilder engine (`.pattern('dag')`/.agent()/.step() chains) that `writing-agent-relay-workflows` and `migrating-persona-to-relayflow` cover — that's a different product despite the similar name.WritingNo warnings★ 1.1K↓ —
- report-issuemicrosoft/power-platform-skillsUse when the user wants a Process Intelligence bug-report draft or support summary for a failed operation.ProductivityNo warnings★ 1.1K↓ —
run-organic-social-account-audit
gooseworks-ai/goose-skills
From the author
Reviews a brand's own social accounts: what each is for, the last ~30 posts ranked against the account's own median with the likely reason for top and bottom posts, cadence actually kept, best posting times, and bio and pinned-post fixes. Use alone when you already know which accounts to review and can read their posts; otherwise run run-organic-social.
Install
npx skills add gooseworks-ai/goose-skills --skill run-organic-social-account-audit -a claude-code
Installs to .claude/skills/run-organic-social-account-audit/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
What it can touch
Safety checks on SKILL.md
No warnings.
Why 88
Files (2)
- SKILL.md
- skill.meta.json