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,492 skills from 2,391 repositories · updated 1 hour ago
48,451 skills
- rendering-strategieskostja94/marketing-skillsWhen the user wants to choose or optimize rendering strategy for SEO. Also use when the user mentions "SSR," "SSG," "CSR," "ISR," "static rendering," "dynamic rendering," "server-side rendering," "client-side rendering," "JavaScript rendering," "pre-rendering," "prerender," "content in initial HTML," or "crawler visibility." For crawl issues, use site-crawlability.MediaNo warnings★ 1.1K↓ —
- canonical-tagkostja94/marketing-skillsAudit and fix duplicate-page canonicalization across protocol, host, slash, default-document, extension, case, and tracking-parameter URL variants. Use for canonical URLs, duplicate content, preferred URLs, URL consolidation, or conflicting canonical signals. For URL naming and hierarchy design, use url-structure.DesignNo warnings★ 1.1K↓ —
- open-source-strategykostja94/marketing-skillsWhen the user wants open source strategy, OSS commercialization, or open source growth. Also use when the user mentions "open source strategy," "OSS strategy," "open source commercialization," "open source to paid," "open core," "COSS," "commercial open source," "GitHub stars strategy," "DevHunt," "open source marketing," "open source growth," "Llama," "Dify," "Cursor," "open source business model," or "developer tools directory." For GitHub tactics, use github.MarketingNo warnings★ 1.1K↓ —
- heading-structureUpdatedkostja94/marketing-skillsWhen the user wants to write or optimize H1-H6, fix heading hierarchy, improve content structure, rewrite an H1, or align headings with page intent. This skill owns actual heading changes; page-metadata may only check and report metadata-to-heading alignment.WritingNo warnings★ 1.1K↓ —
- gtm-strategykostja94/marketing-skillsWhen the user wants to plan go-to-market strategy, GTM framework, or market entry. Also use when the user mentions "GTM," "go-to-market," "market entry," "new market," "repositioning," "PLG," "sales-led," "product-led," "marketing-led," "ICP," "buyer persona," "GTM motion," or "market expansion." For launch checklist, use product-launch.MarketingNo warnings★ 1.1K↓ —
- meta-descriptionkostja94/marketing-skillsWhen the user wants to write, audit, or optimize a meta description, SEO description, SERP snippet candidate, duplicate description, description length, or description rewrite issue. For a sitewide metadata lifecycle including implementation and production validation, use page-metadata.MarketingNo warnings★ 1.1K↓ —
- video-optimizationkostja94/marketing-skillsWhen the user wants to optimize videos for Google Search, video sitemap, VideoObject schema, or video SEO on websites. Also use when the user mentions "video SEO," "video sitemap," "VideoObject," "video thumbnail," "video indexing," "video preview," "key moments," "Clip schema," or "embedded video optimization." For page template, use article-page-generator.MediaNo warnings★ 1.1K↓ —
- brooks-testUpdatedhyhmrright/brooks-lintTest quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares test files for review, or expresses frustration: "tests keep breaking whenever I change anything", "our tests take forever", "tests pass but bugs still reach production", or "we have too many mocks". Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.TestingNo warnings★ 1.6K↓ —
- cell-submissionbrycewang-stanford/Awesome-Journal-SkillsUse as the final preflight before submitting to Cell — a complete checklist across significance, narrative, Highlights/eTOC/Graphical Abstract, Summary, figures, STAR Methods, data, references, and required files. Bundles the checklist and cover-letter templates.ProductivityNo warnings★ 1.4K↓ —
- vis-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing IEEE VIS evaluations, covering how to match evidence to the contribution type (perceptual study, controlled user study, algorithm benchmark, design-study validation, qualitative work), controlled experiment design with power and effect sizes, CVD-safe and perceptually grounded encoding choices, task taxonomies, and provenance so a TVCG reviewer trusts the result.DesignNo warnings★ 1.4K↓ —
- icdt-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ICDT (International Conference on Database Theory) regular-paper submission for Microsoft CMT readiness, covering the two-step abstract-then-paper deadline in the correct submission cycle, the lipics-v2021 15-page limit excluding references, the clearly-marked appendix read at the PC's discretion, anonymous submission since 2024, the complete-proofs / full-version expectation, and which submission problems are unfixable after the AoE cutoff.DataNo warnings★ 1.4K↓ —
- brooks-auditUpdatedhyhmrright/brooks-lintArchitecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized, or asks "does this follow clean architecture?" or "why does everything depend on everything?". Also triggers for onboarding requests: "explain this codebase to a new developer" or "give me a codebase tour" (use onboarding mode). Do NOT trigger for: PR-level code review (use brooks-review) or line-level refactoring questions — this skill analyzes structural/module-level concerns, not individual functions.PlanningNo warnings★ 1.6K↓ —
- eacl-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an EACL submission before its single ACL Rolling Review cycle deadline, covering ACL-template compliance, the 8-page long / 4-page short content caps, the mandatory Limitations section, the Responsible NLP checklist, anonymization, preprint and resubmission declarations, and the no-fallback-cycle timing trap.LegalNo warnings★ 1.4K↓ —
- colm-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when preparing or auditing a COLM submission on OpenReview — the late-March abstract and full-paper deadlines, the strict 9-page main text, double-blind rules banning acknowledgments and identity links, the Code of Ethics acknowledgment, LLM-usage disclosure, reciprocal-reviewer nomination, and pre-upload risk triage.ScienceNo warnings★ 1.4K↓ —
- kdd-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical section of a KDD paper, where evidence combines quality deltas with scalability and efficiency measurements, temporal-leakage-safe splits, mechanism-isolating ablations, tuning-symmetric baselines, and, for the ADS track, post-launch measurement design that survives the desk check.DesignNo warnings★ 1.4K↓ —
- sci-rebuttalbrycewang-stanford/Awesome-Journal-SkillsUse after Science reviews arrive to triage the decision, prioritize experiments, and draft a point-by-point response that is respectful, evidence-led, and honest about limits. Do not run before the main text is actually revised.ScienceNo warnings★ 1.4K↓ —
- jama-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when running the final pre-submission preflight for a JAMA manuscript — word/format limits, required statements, checklist and flow-diagram files, disclosures, and portal steps. Verifies completeness; it does NOT write or analyze content.WritingNo warnings★ 1.4K↓ —
- brooks-sweepUpdatedhyhmrright/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↓ —
- 404-page-generatorkostja94/marketing-skillsDeprecated compatibility entry for 404 Page construction. This page is now maintained in Pagina; install and use page-builder to build a new 404 Page.OtherNo warnings★ 1.1K↓ —
- blog-page-generatorkostja94/marketing-skillsDeprecated compatibility entry for Blog Index construction. This page is now maintained in Pagina; install and use page-builder to build a new Blog Index.WritingNo warnings★ 1.1K↓ —
- homepage-generatorkostja94/marketing-skillsDeprecated compatibility entry for Homepage construction. This page is now maintained in Pagina; install and use page-builder to build a new Homepage.OtherNo warnings★ 1.1K↓ —
- popl-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when preparing a POPL submission for the single July HotCRP deadline — auditing the 25-pages-of-text acmsmall cap, summary-rejection format rules, full double-blind hygiene for theory papers with public proof repositories, dual-submission exposure, and the final-days upload order before the AoE cutoff.ProductivityNo warnings★ 1.4K↓ —
- twitter-x-postskostja94/marketing-skillsWhen the user wants to create X (Twitter) post copy, threads, or optimize for X platform. Also use when the user mentions "X post," "X thread," "Twitter post," "Twitter thread," "tweet," "tweet copy," "thread," "X marketing," "X content," "post to X," "create X post," or "X post copy." For long-form source, use article-content.MarketingNo warnings★ 1.1K↓ —
- nejm-submissionbrycewang-stanford/Awesome-Journal-SkillsUse as the final preflight before submitting to NEJM — a complete clinical checklist across significance, registration, reporting guidelines, abstract, statistics, display items, ethics, references, and required files. Bundles a checklist and a clinical cover-letter template.ScienceNo warnings★ 1.4K↓ —
mariadb-operator-release-notes
mariadb-operator/mariadb-operator
From the author
Create the release notes and upgrade guide for a mariadb-operator release. Given the release PR whose body lists every PR included in the release, it gathers each PR, groups the changes by relevance, and produces `docs/releases/RELEASE_<version>_HEADER.md.gotmpl` and `docs/releases/UPGRADE_<version>.md` in the format the previous releases use, then opens a PR targeting `release-<version>`. If no release PR is provided it asks for the new version and infers the changes from git history since the last tag. Use whenever the user wants release notes, an upgrade/update guide, or docs for a new mariadb-operator version — "create the release notes for 26.10.0", "write the upgrade guide", "document this release", "prepare the release PR docs" — even if they don't mention a release PR.
Install
npx skills add mariadb-operator/mariadb-operator --skill mariadb-operator-release-notes -a claude-code
Installs to .claude/skills/mariadb-operator-release-notes/ · 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 (1)
- SKILL.md