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 71 of 152
- View details
integrate-anythingSkillDocs & knowledge
This skill should be used only when an external-app action must be executed through the Membrane CLI and an authenticated Membrane connection, such as sending a message, creating a task, or syncing records. It should not be used for general API design, SDK integration, documentation lookup, or direc
Ready to connect★ 175
- View details
msagljsSkillDocs & knowledge
Use MSAGL-JS (Microsoft Automatic Graph Layout) to lay out and visualize networks in JavaScript or TypeScript. Use for graph and network layout, DOT/JSON/JGF parsing, live embedded SVG or WebGL graphs, Sugiyama/MDS/IPSepCola layouts, edge routing, and exporting SVG, PDF, PNG, EPS, or PostScript figu
Ready to connect★ 175
- View details
powerbi-documentationSkillDocs & knowledge
Create standardized documentation for Power BI semantic models and reports. Use when the user requests documentation for a Power BI project, semantic model, or report (e.g., "document this model", "create documentation for this Power BI project", "generate documentation"). This skill works with the
Ready to connect★ 175
- View details
compoundSkillDocs & knowledge
This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR. Extracts knowledge from PR context and saves to docs/learnings/.
Ready to connect★ 174
- View details
context-window-designSkillDocs & knowledge
Designing around token limits, memory, and conversation persistence.
Ready to connect★ 173
- View details
state-managementSkillDocs & knowledge
Managing shared context, memory, and state across multiple agents.
Ready to connect★ 173
- View details
iso-24495-3SkillDocs & knowledge
Sector-specific Plain Language standard for science and technical writing (ISO 24495-3:2026). Applied during software documentation, architecture specs, and technical analysis.
Ready to connect★ 172
- View details
iso-24495-5SkillDocs & knowledge
Provisional sector-specific Plain Language standard for document design (based on ISO/WD 24495-5, under development). Applied when structuring complex documents so readers can find and navigate content through layout, visual hierarchy, and navigation aids.
Ready to connect★ 172
- View details
- View details
content-translatorSkillDocs & knowledge
Translate text content between languages with high quality and natural phrasing. Covers document translation, content localization, and multi-language research support for teams working across language barriers.
Ready to connect★ 164
- View details
youtube-transcriptSkillDocs & knowledge
Extract full transcripts and captions from YouTube videos for content analysis, summarization, note-taking, and repurposing. Supports multiple languages and auto-generated captions. Ideal for research, content creation, and accessibility workflows.
Ready to connect★ 164
- View details
obsidian-plugin-qualitySkillDocs & knowledge
Audit ZettelFlow against the official Obsidian plugin guidelines and the Community-hub automated review / quality score. Use before a release, when preparing a directory submission, or when the user asks to "check plugin quality", "raise the Obsidian score", "run the reviewer", or "prepare for submi
Ready to connect★ 168
- View details
sddSkillDocs & knowledge
The Spec-Driven Development pipeline for ZettelFlow — the end-to-end flow (constitution → specify → plan → tasks → implement → verify) and which skill/agent owns each stage. Use when starting any non-trivial change, picking up an issue (especially obsidian-score work), or when the user asks to "foll
Ready to connect★ 168
- View details
specifySkillDocs & knowledge
Stage 1 of the SDD pipeline — write a ZettelFlow spec into a GitHub issue body (problem, value, functional requirements, testable acceptance criteria, capability disclosure, out-of-scope). Use when the user says "specify", "write a spec", "spec out issue #N", or starts new non-trivial work. Delegate
Ready to connect★ 168
- View details
tasksSkillDocs & knowledge
Stage 3 of the SDD pipeline — turn a ZettelFlow plan (in a GitHub issue comment) into an ordered TDD task checklist posted as a second issue comment. Each task has the failing test to write first and the guardrail that proves it. Use after a plan comment exists and the user says "break this into tas
Ready to connect★ 168
- View details
cache-notesSkillDocs & knowledge
Fetch & embed AI transcripts as Obsidian callouts. Args: <path>, all, refresh <path>. Prompts for URLs if empty.
Ready to connect★ 165
- View details
fill-participantsSkillDocs & knowledge
Resolve and fill Participants frontmatter + link unlinked names in body. Args: <path>, all.
Ready to connect★ 165
- View details
followup-todosSkillDocs & knowledge
Extract action items as plain markdown bullets (with confirmation). Args: <path>. No args = run [/note-status pending --step=todos](../note-status/SKILL.md#pending-mode).
Ready to connect★ 165
- View details
last-1on1SkillDocs & knowledge
Show when you last had a 1:1 with each direct report / peer, sorted by recency. Flags people who haven't had one in N weeks. Powered by the OneOnOnes view on Meetings.base.
Ready to connect★ 165
- View details
mail-transcriptsSkillDocs & knowledge
Gmail AI transcript notifications → meeting Notes: URLs + mark read. Args: (none). Invoked standalone or as step 1 of /meeting wrap.
Ready to connect★ 165
- View details
meetingSkillDocs & knowledge
Create or wrap meeting notes. Args: {title} [folder=X], wrap <path>, wrap pending [today|this week|dates]. No args = pick from Google Calendar.
Ready to connect★ 165
- View details
note-statusSkillDocs & knowledge
Verify meeting notes are fully processed. Args: <path>, [dates], all, pending [dates] [--step=X]. Shows which wrap steps are complete or missing.
Ready to connect★ 165
- View details
otter-fetchSkillDocs & knowledge
Fetch Otter.ai transcript data. Sub-skill used by cache-notes and fill-participants when Notes: contains an Otter URL.
Ready to connect★ 165
- View details
people-stubsSkillDocs & knowledge
Batch-create Teams/People/@Name.md stubs from unresolved [[@*]] wikilinks across the vault. Each stub is minimal frontmatter; the user fills team/role/details later.
Ready to connect★ 165
- View details
quark-onnx-doc-drift-checkSkillDocs & knowledge
Compare ONNX skill contracts and guidance against current Quark ONNX documentation and source entry points. Use when maintainers need to verify that ONNX install docs, custom-op registry, QConfig fields, preset and calibration lists, AutoSearchPro presets, deployment-target gates, or example-script
Ready to connect★ 166
- View details
quark-torch-doc-drift-checkSkillDocs & knowledge
Compare skill contracts and guidance against current Quark documentation and source entry points. Use when maintainers need to verify that installation docs, artifact schemas, PTQ planning assumptions, CLI flags, or supported model lists still match upstream Quark reality. Trigger for "check doc dri
Ready to connect★ 166
- View details
quark-torch-file2file-quantizationSkillDocs & knowledge
Low-memory file2file quantization for very large safetensors LLMs that cannot be loaded whole. Use when the user wants to run file2file quantization, adapt a new safetensors checkpoint without loading the full model, register an external LLMTemplate, inspect sharded checkpoint naming, generate wrapp
Ready to connect★ 166
- View details
recapSkillDocs & knowledge
Produce a weekly/date-range recap from emails, Slack, Jira/Confluence, and vault notes. Args: [dates]. Default = this week.
Ready to connect★ 165
- View details
sprint-retroSkillDocs & knowledge
Draft a Sprint Retro by synthesizing scrum dailies, recaps, the sprint planning note, and the prior retro. Args: [sprint number | dates]. No args = infer the current sprint.
Ready to connect★ 165
- View details
sync-upstream-obsidianosSkillDocs & knowledge
Pull structural updates from upstream ObsidianOS into the local vault.
Ready to connect★ 165
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.