Skills.
Give your AI a better way to work.
A skill is a set of written instructions that teaches an AI how to do one job the way it should be done: review a pull request, plan a migration, write the release notes.
Install one here and it travels with your account into Claude, Claude Code, Cursor and every other client you sign in with.
Category: Docs & knowledge
4,535 results · page 38 of 152
- View details
zhihu-transcribeSkillDocs & knowledge
Zhihu video → download → transcribe → save as Markdown. Supports Zhihu video links, no login required.
Ready to connect★ 671
- View details
Architecture Diagram CreatorSkillDocs & knowledge
Create comprehensive HTML architecture diagrams showing data flows, business objectives, features, technical architecture, and deployment. Use when users request system architecture, project documentation, high-level overviews, or technical specifications.
Ready to connect★ 670
- View details
codebase-documenterSkillDocs & knowledge
Generates comprehensive documentation explaining how a codebase works, including architecture, key components, data flow, and development guidelines. Use when user wants to understand unfamiliar code, create onboarding docs, document architecture, or explain how the system works.
Ready to connect★ 670
- View details
project-bootstrapperSkillDocs & knowledge
Sets up new projects or improves existing projects with development best practices, tooling, documentation, and workflow automation. Use when user wants to start a new project, improve project structure, add development tooling, or establish professional workflows.
Ready to connect★ 670
- View details
review-implementingSkillDocs & knowledge
Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.
Ready to connect★ 670
- View details
technical-doc-creatorSkillDocs & knowledge
Create HTML technical documentation with code blocks, API workflows, system architecture diagrams, and syntax highlighting. Use when users request technical documentation, API docs, API references, code examples, or developer documentation.
Ready to connect★ 670
- View details
amazon-category-ungatingSkillDocs & knowledge
Category and brand ungating — requirements, documentation, appeal process, restricted categories guide
Ready to connect★ 667
- View details
amazon-product-complianceSkillDocs & knowledge
Product compliance and safety — certifications, labeling requirements, restricted substances, documentation
Ready to connect★ 667
- View details
define-problem-statementSkillDocs & knowledge
Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.
Ready to connect★ 665
- View details
deliver-edge-casesSkillDocs & knowledge
Documents edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for. Use during specification to map the failure surface and ensure comprehensive coverage, or during QA planning t
Ready to connect★ 665
- View details
deliver-prdSkillDocs & knowledge
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.
Ready to connect★ 665
- View details
deliver-release-notesSkillDocs & knowledge
Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language. Use when shipping updates to communicate changes to users, customers, or stakeholders.
Ready to connect★ 665
- View details
develop-adrSkillDocs & knowledge
Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.
Ready to connect★ 665
- View details
develop-design-rationaleSkillDocs & knowledge
Documents the reasoning behind design decisions including alternatives considered, trade-offs evaluated, and principles applied. Use when making significant UX decisions, aligning with stakeholders on design direction, or preserving design context for future reference.
Ready to connect★ 665
- View details
develop-spike-summarySkillDocs & knowledge
Documents the results of a completed technical or design spike, capturing the original question, approach, evidence-backed findings, and a clear proceed-or-not recommendation so the team does not re-litigate the exploration. Use once a time-boxed investigation has concluded. For the architecture dec
Ready to connect★ 665
- View details
discover-journey-mapSkillDocs & knowledge
Maps a customer journey across stages, touchpoints, emotional curve, pain points, and moments of truth into a markdown artifact with an optional mermaid timeline or flowchart. Use when synthesizing existing research into the shape of a customer's experience, end-to-end or for one phase. Without rese
Ready to connect★ 665
- View details
foundation-meeting-briefSkillDocs & knowledge
Produces a private strategic preparation document for the user before a meeting that matters. Captures stakes, stakeholder positions and reads, ranked desired outcomes, key messages, anticipated questions with prepared responses, risks and tensions, specific asks, and success signals. Distinct from
Ready to connect★ 665
- View details
foundation-meeting-synthesizeSkillDocs & knowledge
Cross-meeting archaeology skill. Consumes multiple meeting recaps (or raw notes) over a period and surfaces patterns invisible in any single meeting. Shows how decisions evolved, who has been saying what, where threads are stalling, and where contradictions have emerged. Produces a plain-text timeli
Ready to connect★ 665
- View details
foundation-prioritized-action-planSkillDocs & knowledge
Produce a comprehensive, evidence-grounded prioritized action plan from any PM input (notes, transcripts, drafts, executive asks, Slack threads, or a raw situation). Outputs one saveable document with an executive summary, input mirror, situation classification (Cynefin), the binding constraint (The
Ready to connect★ 665
- View details
foundation-stakeholder-briefingsSkillDocs & knowledge
Turns any source artifact (spec, discovery, research, GTM plan, experiment results, retro, or raw notes) into one canonical master document plus a set of audience-tailored briefings, each re-pitched to a stakeholder lens (executive, board, engineering, UX, PMM, sales, CS, legal, data, or a custom au
Ready to connect★ 665
- View details
foundation-stakeholder-updateSkillDocs & knowledge
Produces async communication to stakeholders, primarily non-attendees and secondarily some attendees who want a reference. Translates meeting outcomes into what-it-means language for readers, with channel variants (slack, teams, email, notion, exec-memo) and audience variants (engineering, design, l
Ready to connect★ 665
- View details
iterate-lessons-logSkillDocs & knowledge
Creates a structured lessons learned entry for organizational memory. Use after an incident, a completed project, or a significant learning to record knowledge for future teams and initiatives. Distinct from iterate-retrospective, which facilitates the team ceremony; this skill writes the durable le
Ready to connect★ 665
- View details
iterate-pivot-decisionSkillDocs & knowledge
Documents a strategic pivot or persevere decision with the evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.
Ready to connect★ 665
- View details
iterate-refinement-notesSkillDocs & knowledge
Documents backlog refinement session outcomes including stories refined, estimates, questions raised, and decisions made. Use during or after refinement to capture the results and share with absent team members.
Ready to connect★ 665
- View details
iterate-retrospectiveSkillDocs & knowledge
Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of a sprint, project, or milestone to reflect and improve team practices. To bank individual learnings into organizational memory afterward, use iterate-lessons-log.
Ready to connect★ 665
- View details
measure-experiment-resultsSkillDocs & knowledge
Documents the results of a completed experiment or A/B test with statistical analysis, learnings, and recommendations. Use after experiments conclude to communicate findings, inform decisions, and build organizational knowledge.
Ready to connect★ 665
- View details
tool-design-sprint-map-and-targetSkillDocs & knowledge
Day 1 (Monday) move of a Design Sprint that produces the bundled Monday artifact containing long-term goal, sprint questions (3-7 testable risks), customer or system map (5-15 step flow), expert interview notes, HMW (How Might We) cluster board, and the Decider's chosen target moment. Use Day 1 morn
Ready to connect★ 665
- View details
tool-design-sprint-sketchSkillDocs & knowledge
Day 2 (Tuesday) move of a Design Sprint that structures lightning demos and the four-step independent solution sketch protocol (Notes, Ideas, Crazy 8s, Solution Sketch). Each team member produces one solution sketch individually; the skill orchestrates the day but does not author the sketches themse
Ready to connect★ 665
- View details
tool-note-and-voteSkillDocs & knowledge
Structured group-decision mechanic that captures silent ideation, voting summaries, and Decider sign-off in a single bundled artifact. Use when a small team needs to make a fast decision with diverse input, when groupthink is a risk, or when a workshop moment demands silent contribution before discu
Ready to connect★ 665
- View details
utility-slideshow-creatorSkillDocs & knowledge
Generates professional presentations from a JSON deck specification using 18 slide types with dark/light variants, content-to-layout decision logic, and calibrated character limits. Ships with a default professional theme.
Ready to connect★ 665
What is a skill?
A skill is plain text, usually a SKILL.md file and the scripts it refers to, written for an AI rather than for a person. It carries the steps, the house rules and the examples a good answer needs, so you stop pasting the same briefing into every new chat.
54,764 of the 55,196 skills listed here can be served through ahel today, and they come from public repositories. Each one has its own page with the instructions themselves on it, so you can read what a skill will tell your AI to do before you install it.
Install one and every AI you use gets it
Installing a skill adds it to your gateway and turns it on in the same step. Claude Code surfaces it as a slash command; any client can read the full instructions with the skill_read tool.
Nothing is copied into a project folder. The instructions are served from your account, so the same skill is there in every AI you connect, and turning it off removes it from all of them at once.