Agenttien taidot
Taidot Claude Codelle, Codexille, Cursorille ja muille agenteille skills.sh-hakemistosta: asennukset, tietoturvatarkastuksen tila ja komento taidon lisäämiseen.
Skill ei ole sidottu yhteen agenttiin: npx skills add asentaa sen mihin tahansa tuettuun agenttiin. Ilman -a-valitsinta CLI etsii tietokoneesi agentit ja kysyy, mihin se lisätään.
Päivitetty · Lähteet: skills.sh
Näytetään: 100 · löytyi: 150 · / 10 000 hakemistossa
-
grill-with-docs mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
1 117 836 Hyväksytty -
lark-shared larksuite/cli
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling _notice JSON.
460 340 Hyväksytty -
repo-intake-and-plan lllllllama/rigorpilot-skills
Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.
450 248 Hyväksytty -
env-and-assets-bootstrap lllllllama/rigorpilot-skills
Rigor Setup skill for README-first deep learning repo reproduction. Use when the task is specifically to prepare a conservative conda-first environment, checkpoint and dataset path assumptions, cache location hints, and setup notes before any run on a README-documented repository. Do not use for repo scanning, full orchestration, paper interpretation, final run reporting, or generic environment setup that is not tied to a specific reproduction target.
450 084 Hyväksytty -
writing-beats mattpocock/skills
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
424 650 Hyväksytty -
writing-shape mattpocock/skills
Writing, exploit: shape raw material into an article, paragraph by paragraph.
424 155 Hyväksytty -
writing-fragments mattpocock/skills
Writing, explore: mine raw fragments, no structure yet.
423 738 Hyväksytty -
writing-for-agents mattpocock/skills
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
380 843 Hyväksytty -
lark-markdown larksuite/cli
飞书 Markdown：查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件，或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。
371 142 Hyväksytty -
pr-to-video heygen-com/hyperframes
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
327 061 Hyväksytty -
writing-great-skills mattpocock/skills
306 525 Hyväksytty -
writing-plans obra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
266 605 Hyväksytty -
writing-skills obra/superpowers
Use when creating new skills, editing existing skills, or verifying skills work before deployment
204 307 Hyväksytty -
obsidian-markdown kepano/obsidian-skills
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
89 010 Hyväksytty -
gws-docs-write googleworkspace/cli
Google Docs: Append text to a document.
47 990 Hyväksytty -
golang-documentation samber/cc-skills-golang
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices. Triggers for both libraries and applications/CLIs.
37 080 Hyväksytty -
golang-swagger samber/cc-skills-golang
Golang OpenAPI/Swagger documentation with swaggo/swag — annotation comments (@Summary, @Param, @Success, @Router, @Security), swag init code generation, framework integrations (gin, echo, fiber, chi, net/http), security definitions (Bearer/JWT, OAuth2, API key), and struct tags (swaggertype, enums, example, swaggerignore). Apply when adding or maintaining Swagger/OpenAPI docs in a Go project, or when the codebase imports github.com/swaggo/swag, github.com/swaggo/gin-swagger, github.com/swaggo/echo-swagger, github.com/swaggo/http-swagger, or github.com/swaggo/files.
33 954 Hyväksytty -
recipe-create-doc-from-template googleworkspace/cli
Copy a Google Docs template, fill in content, and share with collaborators.
29 685 Hyväksytty -
recipe-generate-report-from-sheet googleworkspace/cli
Read data from a Google Sheet and create a formatted Google Docs report.
29 500 Hyväksytty -
recipe-share-doc-and-notify googleworkspace/cli
Share a Google Docs document with edit access and email collaborators the link.
29 221 Hyväksytty -
recipe-post-mortem-setup googleworkspace/cli
Create a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat.
28 823 Hyväksytty -
baoyu-format-markdown jimliu/baoyu-skills
Formats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or improve article layout. Outputs to {filename}-formatted.md.
27 694 Hyväksytty -
better-writing jakubkrehel/skills
Focuses on improving product copy in your project.
24 389 Hyväksytty -
architecture-decision-records wshobson/agents
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
19 345 Hyväksytty -
write-feature-docs warpdotdev/common-skills
Draft a complete documentation page for a new Warp feature from its PRODUCT.md and/or TECH.md spec. Use when an engineer has written a spec and needs to produce a first-pass MDX draft for the warpdotdev/docs repo. Also handles features without specs by researching the codebase first. Invoke this skill whenever an engineer mentions writing docs for a feature, drafting a docs page, creating feature documentation, starting the eng-docs workflow, or converting a spec into documentation. Requires an interactive session with the engineer present - it confirms a content design plan, then an outline, before drafting, and cannot run unattended. For automated, release-triggered docs, use the missing_docs skill in warpdotdev/docs instead. Works from warp-internal or warp-server.
18 190 Hyväksytty -
python-code-style wshobson/agents
Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.
15 711 Hyväksytty -
nature-writing yuan1z0825/nature-skills
Draft or restructure scientific manuscript arguments, sections, and initial-submission materials from author-provided evidence. Use for 论文写作、章节起草、论证重构、正文压缩、首次投稿材料. Use nature-polishing for language-only edits to existing prose and nature-response for post-decision correspondence.
13 701 Hyväksytty -
changelog-automation wshobson/agents
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
13 250 Hyväksytty -
writing hookify rules anthropics/claude-code
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
12 805 Hyväksytty -
technical-writing riekelt/technical-writer
Use when writing, restructuring, or revising any technical document - specs, design docs, READMEs, reference documentation, plans, reports - or any prose that must survive being read twice by someone in a hurry. Encodes the house style, the truth and sourcing rules, and the banned-constructions list. Use whenever you produce repository-bound text longer than a paragraph, even if nobody says "document". Foundation for the sibling document-type skills.
12 752 Hyväksytty -
writing-design-docs riekelt/technical-writer
Use when writing a proposal, RFC, design document, spec, or migration plan - anything that argues for a change, records a design, or asks readers for input on one. Encodes the proposal skeleton, the Why & What decision box, and the completeness checks. Use whenever a change needs arguing or scoping in writing, even if the user just says "write up the approach".
12 445 Hyväksytty -
writing-runbooks riekelt/technical-writer
Use when writing operational documentation - runbooks, setup guides, release procedures, migration guides, deprecation guides, troubleshooting entries, or any ordered procedure someone will execute under time pressure. Encodes the runbook skeleton, the risk legend, the symptom-first troubleshooting format, and the migration-guide rules (mapping table, mandatory rollback, deprecation dates, built-in expiry). Use whenever someone will execute the text, even if it is called a "guide" or "setup notes".
12 355 Hyväksytty -
writing-changelogs riekelt/technical-writer
Use when writing a changelog entry, release notes, or a "what shipped" summary after completing work. Encodes the entry shape, the handover template, and the honesty conventions. Use after shipping meaningful work, even if the user just says "summarize what we did".
12 352 Hyväksytty -
writing-unit-tests riekelt/principal-engineer
Use when writing or refactoring unit tests - a new test file, added cases, a flaky test, an unreadable one. Encodes behavior-first testing: one behavior per test, names that state the claim, deterministic setup, mocks only at boundaries you do not own. Use whenever a test is being written, even a quick one, and whenever a test needs a sleep, a mock of your own code, or a copy of the implementation's math.
12 280 Hyväksytty -
documenting-legacy-codebases riekelt/technical-writer
Use when documenting an existing codebase whose documentation is missing, stale, or untrusted - an inherited system, a legacy application, a repo where the docs lie - or when regrounding a documentation tree against the code, or when someone asks what a system actually does. Encodes the survey-first inventory, the writer-side evidence hierarchy, depth-per-surface rules, the refactor test, dead-or-alive proofs, the quirks-and-findings split, the coverage ledger, the parallel campaign, and the docs-tree skeleton. Use whenever documentation must be reconstructed from the code rather than written alongside a change.
12 226 Hyväksytty -
svelte-code-writer sveltejs/ai-tools
CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
11 695 Hyväksytty -
article-writing affaan-m/ecc
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
11 084 Hyväksytty -
convert-documents-to-markdown firecrawl/anydoc
Convert Word (.doc, .docx), PowerPoint (.ppt, .pptx), Excel (.xls, .xlsx), OpenDocument (.odt, .ods, .odp), RTF, EPUB, CSV, and PDF files to GitHub-Flavored Markdown. Use when a task needs the contents of an office document, spreadsheet, presentation, ebook, or PDF you cannot read directly.
10 940 Hyväksytty -
postmortem-writing wshobson/agents
Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response processes.
10 305 Hyväksytty -
h3-prompt-writing minimax-ai/minimax-h3
Write MiniMax H3 video generation prompts for T2VA, I2VA, FL2VA, L2VA, and Ref2VA. Use when rewriting multimodal requests into H3 prompt structures, composing integrated_multimodal_description, overall_soundscape, and non_diegetic_music, aligning keyframes, or defining reference labels for images, videos, and audio.
10 099 Hyväksytty -
architecture-decision-records affaan-m/ecc
Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README. Use when the user says 'record this decision' or 'ADR this', chooses between frameworks or databases, discusses trade-offs, or asks why the codebase is shaped this way.
9 290 Hyväksytty -
technology-stack-blueprint-generator github/awesome-copilot
Comprehensive technology stack blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks, programming languages, and implementation patterns across multiple platforms (.NET, Java, JavaScript, React, Python). Generates configurable blueprints with version information, licensing details, usage patterns, coding conventions, and visual diagrams. Provides implementation-ready templates and maintains architectural consistency for guided development.
8 999 Hyväksytty -
update-markdown-file-index github/awesome-copilot
Update a markdown file section with an index/table of files from a specified folder.
8 930 Hyväksytty -
customs-trade-compliance affaan-m/ecc
Codified customs and trade compliance expertise — HS/HTS tariff classification with GRI rules, commercial invoices and entry documentation, Incoterms 2020, FTA qualification and duty optimization (USMCA, RCEP, FTZs, drawback), denied-party screening, and penalty mitigation across US, EU, UK, and APAC jurisdictions. Use when classifying goods, preparing import/export documentation, screening restricted parties, responding to customs audits or CF-28/penalty notices, or optimizing duties.
8 841 Hyväksytty -
update-llms github/awesome-copilot
Update the llms.txt file in the root folder to reflect changes in documentation or specifications following the llms.txt specification at https://llmstxt.org/
8 830 Hyväksytty -
tldr-prompt github/awesome-copilot
Create tldr summaries for GitHub Copilot files (prompts, agents, instructions, collections), MCP servers, or documentation from URLs and queries.
8 763 Hyväksytty -
msw-search msw-git/msw-ai-coding-plugins-official
MSW search integration — (1) vector search for API docs and implementation guides via the msw-mcp MCP server (mlua_api_retriever / mlua_document_retriever), (2) REST API search for resources (sprite / animation / sound / resource pack / avatar). Use for 'find details, examples, or related APIs not in .d.mlua', 'need a SpriteRUID', 'monster sprite', 'background image', 'find a sound', 'avatar item lookup', etc. Keywords: document search, API details, examples, guide, retriever, resource, sprite, animation, sound, RUID, resource pack, avatar.
8 709 Hyväksytty -
google-workspace-ops affaan-m/ecc
Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents. Use when the user needs to find, summarize, edit, migrate, or clean up Google Workspace assets without dropping to raw tool calls.
7 778 Hyväksytty -
cypress-docs cypress-io/ai-toolkit
Search and extract Cypress information from official documentation (docs.cypress.io, cypress.io); prefer LLM markdown under /llm/* and refuse unverified API or behavior claims.
7 334 Hyväksytty -
cmux-markdown manaflow-ai/cmux
Open markdown files in a formatted viewer panel with live reload. Use when you need to display plans, documentation, or notes alongside the terminal with rich rendering (headings, code blocks, tables, lists).
7 237 Hyväksytty -
changelog-generator composiohq/awesome-claude-skills
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
7 006 Hyväksytty -
update-oo-component-documentation github/awesome-copilot
6 976 Hyväksytty -
hads wshobson/agents
Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.
6 148 Hyväksytty -
dart-write-documentation flutter/agent-plugins
Rules and formatting guidelines for writing Dart /// API documentation and doc comments. Use when documenting Dart code, writing doc comments for any Dart declaration (libraries, classes, methods, variables, etc.), or when instructed to follow the Effective Dart documentation guidelines.
5 935 Hyväksytty -
grill-with-docs vinvcn/mattpocock-skills-zh-cn
一个用来打磨计划或设计的持续追问式访谈，并在过程中创建文档（ADRs 和词汇表）。
5 848 Hyväksytty -
ecc-guide affaan-m/ecc
Answer questions about Everything Claude Code by reading the live repo surface — agents, skills, commands, hooks, rules, install profiles, and docs — instead of memory. Use when the user asks what ECC includes, how to install or reset it, which skill or command fits a task, or how project onboarding works.
5 818 Hyväksytty -
setup-matt-pocock-skills vinvcn/mattpocock-skills-zh-cn
为此仓库配置 engineering skills——设置其 issue tracker、triage labels 词汇与 domain docs 布局。在首次使用其他 engineering skills 前运行一次。
5 553 Hyväksytty -
spec-to-code-compliance trailofbits/skills
Check code against the documentation that specifies it - which requirements hold, which the code contradicts, which are absent, and what the code does that no document mentions. Use when comparing an implementation against a whitepaper, protocol spec, or design document.
5 427 Hyväksytty -
indexion-readme trkbt10/indexion-skills
README construction — initialize template structure, generate per-package READMEs from doc comments, plan writing tasks, assemble root README from docs/ and package READMEs via doc.json config, and verify edits with `plan drift`.
5 097 Hyväksytty -
indexion-documentation trkbt10/indexion-skills
Documentation analysis — assess coverage, detect code-to-doc drift with plan reconcile, visualize dependencies with doc graph. Answers "what needs docs?" and "are docs still accurate?"
4 957 Hyväksytty -
cmux-architecture manaflow-ai/cmux
cmux package architecture, refactor layering, dependency inversion, file organization, DocC documentation, package design discipline, testability, and Swift 6 concurrency rules. Use before adding or meaningfully rewriting Swift files, Swift packages, coordinators, services, repositories, or public package APIs.
4 562 Hyväksytty -
langgraph-docs langchain-ai/deepagents
Fetches and references LangGraph Python documentation to build stateful agents, create multi-agent workflows, and implement human-in-the-loop patterns. Use when the user asks about LangGraph, graph agents, state machines, agent orchestration, LangGraph API, or needs LangGraph implementation guidance.
4 541 Hyväksytty -
cmux-localization manaflow-ai/cmux
Localization rules and audit workflow for cmux UI strings, settings rows, menus, shortcuts, schema/config text, docs, command/help text, alerts, tooltips, and web messages. Use whenever changing user-facing text.
4 464 Hyväksytty -
dart-write-documentation dart-lang/skills
Rules and formatting guidelines for writing Dart /// API documentation and doc comments. Use when documenting Dart code, writing doc comments for any Dart declaration (libraries, classes, methods, variables, etc.), or when instructed to follow the Effective Dart documentation guidelines.
4 330 Hyväksytty -
writing-clearly-and-concisely softaworks/agent-toolkit
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
4 249 Hyväksytty -
c4-architecture softaworks/agent-toolkit
Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include "architecture diagram", "C4 diagram", "system context", "container diagram", "component diagram", "deployment diagram", "document architecture", "visualize architecture".
4 163 Hyväksytty -
crafting-effective-readmes softaworks/agent-toolkit
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
4 142 Hyväksytty -
changelog generator claude-office-skills/skills
Generate release notes from git commits, updates, or feature lists
4 132 Hyväksytty -
markdown assistant-ui/skills
Renders assistant message text as markdown in assistant-ui. Use when wiring MarkdownTextPrimitive or the markdown-text element into MessagePrimitive.Parts, installing Shiki or Prism highlighting, adding KaTeX math or Mermaid diagrams, normalizing model-produced math delimiters, or choosing StreamdownTextPrimitive for block-aware streaming with optional code, math, Mermaid, and CJK plugins. Covers defer and smooth parsing behavior, code block overrides, and stream completion. For the surrounding unstyled message composition use primitives, and for installing or editing a styled renderer use elements.
4 031 Hyväksytty -
qmd tobi/qmd
Search local markdown knowledge bases, notes, docs, and wikis with QMD. Use when users ask to find notes, retrieve documents, inspect a wiki, answer from indexed markdown, or set up QMD access.
3 979 Hyväksytty -
react-useeffect softaworks/agent-toolkit
React useEffect best practices from official docs. Use when writing/reviewing useEffect, useState for derived values, data fetching, or state synchronization. Teaches when NOT to use Effect and better alternatives.
3 938 Hyväksytty -
image-generation zc277584121/marketing-skills
Generate illustration images for articles and documentation with a Codex-first workflow, OpenAI API fallback, and Gemini fallback.
3 812 Hyväksytty -
technical-writing cursor/plugins
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
3 778 Hyväksytty -
jupyter-notebook-writing zc277584121/marketing-skills
Write Milvus application-level Jupyter notebook examples using a Markdown-first workflow with jupyter-switch for format conversion.
3 721 Hyväksytty -
no-mistakes kunchenguid/no-mistakes
Validate your code changes through the no-mistakes pipeline - automated code review, tests, lint, docs, push, PR, and CI - before they reach the configured push target. Use when the user asks to run no-mistakes, gate or ship or validate their changes, push safely, asks you to do a task and then validate it, or invokes /no-mistakes.
3 689 Hyväksytty -
docs-guard amelnagdy/guard-skills
Review generated or changed documentation before it ships — READMEs, API references, docstrings, PHPDoc/JSDoc, changelogs, tutorials, and doc sites. Best used reactively after an agent writes or edits docs, after code changes documented behavior, or before publishing docs. Use when the user says 'review the docs', 'is this documentation accurate', 'update the docs', 'write a README', 'document this API', 'add a docstring', or 'add a changelog entry'. Core job: verify every referenced function, flag, endpoint, config key, and code sample against the source; catch docs-vs-code drift; strip filler and unverifiable claims. DO NOT USE for production code review (use clean-code-guard), test review (use test-guard), marketing copy or blog posts, prose style editing of non-technical writing, or documentation site theming.
3 682 Hyväksytty -
audit jsmastery-pro/skills
Run /audit on a greenfield project, an existing codebase with missing docs, or one area (/audit src/auth) to bootstrap the project's AI context, the AGENTS.md files every later skill reads. Writes tool agnostic AGENTS.md plus thin CLAUDE.md pointers, adding only what is missing; never overwrites curated content.
3 632 Hyväksytty -
scope jsmastery-pro/skills
Run /scope to turn a product idea into a living, coarse scope in docs/scope/ and keep it current: plan a new product, plan the next slice, enroll one named feature, or run with no argument to reconcile after shipping and queue what is next. Seeds WHAT to build; /architect designs, /develop builds.
3 631 Hyväksytty -
document jsmastery-pro/skills
Run /document `pr` | `changelog` | `release-note` | `postmortem` (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
3 627 Hyväksytty -
docs-updater giuseppe-trisciuoglio/developer-kit
Provides automated documentation updates by analyzing git changes between the current branch and the last release tag. Performs git diff analysis to identify modifications, then updates README.md, CHANGELOG.md following Keep a Changelog standard, and discovers documentation folders for contextual updates. Use when preparing a release, maintaining documentation sync, or before creating a pull request. Triggers on "update docs", "update changelog", "sync documentation", "update readme", "prepare release documentation".
3 388 Hyväksytty -
neat-freak kkkkhazix/khazix-skills
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and also on clear knowledge-closeout intent without the name: syncing or tidying project docs/rules/memory after development ("把文档和记忆整理一下", "收尾时把文档同步掉", "docs 和代码对不上了"), stale or conflicting CLAUDE.md/memory, a clean handoff to a teammate or a fresh session, or auditing whether workspace rules are actually followed. Do not trigger for pure coding/refactoring/debugging tasks, tidying data or prose (JSON, 周报, changelog announcements), or a bare "整理" with no project-knowledge context.
3 322 Hyväksytty -
writing-shape vinvcn/mattpocock-skills-zh-cn
Writing, exploit：把原始素材塑造成文章，一段一段地推进。
3 273 Hyväksytty -
writing-fragments vinvcn/mattpocock-skills-zh-cn
Writing, explore：挖掘原始 fragments，暂不施加任何结构。
3 263 Hyväksytty -
writing-beats vinvcn/mattpocock-skills-zh-cn
Writing, exploit——把原始素材组装成一段节拍旅程，在某个 beat 依赖一个术语之前先把它 grounded。
3 255 Hyväksytty -
mintlify mintlify.com
Build and maintain documentation sites with Mintlify. Use when creating docs pages, configuring navigation, adding components, or setting up API references.
3 222 Hyväksytty -
writing-prds refoundai/lenny-skills
Help users transform abstract ideas into actionable project specs that align engineering and design teams on the problem and success metrics.
3 195 Hyväksytty -
blog-writing-guide getsentry/skills
Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.
3 101 Hyväksytty -
developer-docs-structure-audit samber/developer-relations-skills
Audits an existing developer documentation set's structure - a page-by-page inventory classified against the Diátaxis modes (tutorial, how-to, reference, explanation), mixed-mode and misplaced pages, coverage gaps per product surface, navigation drift against the file tree, a CNCF TechDocs rubric score, and a prioritized remediation queue. Use whenever the user mentions a docs structure or content audit, docs information architecture, Diátaxis, "our documentation is a mess", a docs gap analysis, what docs are missing, where a page should live, or reorganizing a documentation site - even if they only say "our docs are hard to navigate". Not for writing pages. Do NOT use for docs search ranking - use samber/developer-relations-skills@docs-seo.
3 084 Hyväksytty -
retrieving-developer-knowledge google/skills
Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.
3 029 Hyväksytty -
provider-docs hashicorp/agent-skills
Create, update, and review Terraform provider documentation for Terraform Registry using HashiCorp-recommended patterns, tfplugindocs templates, and schema descriptions. Use when adding or changing provider configuration, resources, data sources, ephemeral resources, list resources, functions, actions, or guides; when validating generated docs; and when troubleshooting missing or incorrect Registry documentation.
3 007 Hyväksytty -
cli-creator openai/skills
Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read/write commands, return stable JSON, manage auth, and pair with a companion skill.
2 987 Hyväksytty -
docs-code-sample-standards samber/developer-relations-skills
Defines the policy every code sample in developer documentation must meet and audits an existing sample corpus against it, returning a ranked fix queue. Use whenever the user mentions docs code samples, code snippets in documentation, runnable examples, examples that no longer compile, copy-paste failures, snippet drift after an API change, testing docs examples in CI, SDK snippet parity across languages, sample maintenance ownership, or asks why the examples in their docs do not work - even if they only say the docs are broken. Covers sample anatomy, copy-paste and security safety, execution tiers, single-sourcing from tested code, and language parity. Not for writing a quickstart page - use samber/developer-relations-skills@developer-quickstart-guide.
2 982 Hyväksytty -
journal-entry-prep anthropics/knowledge-work-plugins
Prepare journal entries with proper debits, credits, and supporting documentation for month-end close. Use when booking accruals, prepaid amortization, fixed asset depreciation, payroll entries, revenue recognition, or any manual journal entry.
2 858 Hyväksytty -
academic-writing jamditis/claude-skills-journalism
Scholarly writing and research compliance. Use for CRediT, preregistration, Plan S, Nelson Memo, preprints, ORCID, LLM disclosure.
2 855 Hyväksytty -
frontend-design-deslop samber/cc-skills
Designs distinctive, non-generic UI — typography, OKLCH color, design tokens (DESIGN.md), layout, components, motion, dark mode, accessibility — for landing pages, SaaS apps, dashboards, ecommerce, decks, docs, portfolios, avoiding the AI-slop / Claude-esque default look. Use whenever building or styling any web frontend, app, dashboard, landing page, deck, or artifact, or when the user says "make it not look like AI", "de-slopify", "deslop", "less generic", "give it character", "design a UI for X", "design an app", "update DESIGN.md", or complains the output looks like every other AI site. Trigger even on a bare "build a UI for X" with no aesthetic named. Not for writing marketing copy.
2 834 Hyväksytty -
design-cleanup gjkim42/kanon-repo
Sweep the current branch for leftovers of an abandoned design after a significant mid-work decision change, and rewrite the affected code, comments, tests, and docs so the result reads as if it had been designed this way from the beginning. Use when the user says "design cleanup", "clean up the old approach", "erase the journey", says a design decision changed and asks to clean up after it, or after a pivot in approach mid-branch. This is a rewrite pass over the code touched by the decision only — not a general refactoring or bug-hunting pass.
2 808 Hyväksytty -
theme-factory nexu-io/open-design
Apply professional font and color themes to artifacts including slides, docs, reports, and HTML landing pages. Ships 10 pre-set themes.
2 675 Hyväksytty -
animated-readme-logo stark-ai-de/agent-skills
Create, transform, animate, or audit GitHub README logos and their verified SVG/PNG/GIF delivery. Use when a repository needs branding assets, not ordinary README prose or app/site motion.
2 625 Hyväksytty -
image-enhancer nexu-io/open-design
Improve image and screenshot quality by enhancing resolution, sharpness, and clarity for professional presentations and documentation.
2 610 Hyväksytty -
stripe-docs stripe/ai
Use when the user or agent needs to read, search, or look up Stripe documentation or API reference. Prefer this over curl or WebFetch for any docs.stripe.com content. Use to fetch gated documentation.
2 492 Hyväksytty
Kuvaukset ovat tekijöiden omia ja englanninkielisiä. Lue taidon koodi sen repositoriosta ennen asentamista.
Mikä on taito?
Taito on kansio, jossa on SKILL.md-tiedosto ja mahdollisesti skriptejä, ja agentti lataa sen, kun tehtävä sopii siihen. Taito voi opettaa agentille tietyn tiedostomuodon käsittelyn, tietyn työnkulun tai työkalun käytön. Hakemisto näyttää skills.sh:n taidot Claude Codelle, Codexille, Cursorille ja muille agenteille: nimi, tekijä ja koodivarasto, asennusten määrä, tietoturvatarkastuksen tila ja komento taidon lisäämiseen.
Miten hakemisto on koottu
- 10 000 asennetuinta taitoa, synkronoitu päivittäin skills.sh:sta.
- ”Nousussa” tarkoittaa viimeisten 7 päivän aikana kertyneitä asennuksia.
- Suodattimet aiheen ja agentin mukaan sekä haku; enintään 100 taitoa näkymää kohden.
- Painike ”Kopioi komento” kopioi asennuskomennon.
Kuvaukset ovat tekijöiden omia, englanniksi, eikä niitä käännetä. Asennukset laskee skills.sh.
Tietoturvatarkastuksen tilat
Jokaisella taidolla on yksi neljästä tilasta skills.sh:n julkaisemien tarkastusten perusteella: ”Hyväksytty”, ”Varoituksia”, ”Hylätty” tai ”Ei tarkastettu”. Hyväksytty tarkastus ei ole takuu. Taito voi ajaa skriptejä koneellasi agentin oikeuksin, joten lue koodi koodivarastosta ennen asennusta.
Näin löydät hyvän taidon
- Suodata oman agenttisi ja työsi aiheen mukaan.
- Katso asennuksia ja ”Nousussa”-merkintää alustavana vihjeenä, ei laatuleimana.
- Avaa koodivarasto GitHubissa ja lue SKILL.md sekä mahdolliset skriptit.
- Asenna, kokeile testiprojektissa ja poista taidot, joita et käytä.
Esimerkkejä taidoista
Taitoja on testien kirjoittamiseen, pull requestien läpikäyntiin, taulukoiden ja PDF-tiedostojen käsittelyyn, käyttöliittymien rakentamiseen suunnittelujärjestelmän mukaan ja yrityksen koodityylin noudattamiseen. Osa on pieniä ja sisältää vain ohjeita, osa ajaa komentoja skripteillä. Mitä enemmän taito tekee, sitä tärkeämpää on lukea koodi ensin.
Mihin taidot sopivat?
Taidot parantavat agenttia tietyissä tehtävissä, mutta eivät korvaa hyvää mallia. Valitse ensin agentti koodausagenttien sivulta ja laajenna sitä sitten taidoilla.