スキルレーダー · GITHUB

実際に使われている Agent Skills。

公開リポジトリの検証済み Skills を比較し、機能、内容、導入状況、出典を確認してから追加できます。

掲載範囲
検証済み
Skills
5,771
リポジトリ
824
最終同期
2026/09/08
5,771 Skills
cap-go
コミュニティ

webapp-to-capacitor

Guide for migrating an existing web app, PWA, or SPA into a store-ready Capacitor iOS and Android app. Use this skill when users want to wrap or convert a web app into a mobile app, avoid thin WebView app store rejection, add native-feeling UX, handle permissions, offline behavior, account deletion, billing, testing, and Capgo live updates.

導入数
2
GitHub Stars
68
更新日
7月13日
qianwen-ai
コミュニティ

qianwen-find-skills

Discover, compare, and optionally install published Agent Skills from QianWen. TRIGGER when: user asks to find or recommend a skill, asks whether a skill exists for a task, wants to browse skills by category, wants to compare candidates, asks to install a discovered skill, or explicitly invokes this skill by name (e.g. use qianwen-find-skills). DO NOT TRIGGER when: user already selected an installed skill and only wants to run it, or the request is unrelated to skill discovery or installation.

導入数
2
GitHub Stars
88
更新日
9月4日
qianwen-ai
コミュニティ

qianwen-text

Generate text, have conversations, write code, reason, and call functions with Qwen models. TRIGGER when: user asks to chat with Qwen, generate text, write code with Qwen, use Qwen function calling, or explicitly invokes this skill by name (e.g. use qianwen-text). DO NOT TRIGGER when: general coding questions without Qwen, non-Qwen AI model usage (OpenAI, Gemini, etc.), image/video understanding (use qianwen-vision), image/video/audio generation.

導入数
2
GitHub Stars
88
更新日
9月4日
cline
コミュニティ

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

導入数
2
GitHub Stars
23
更新日
7月21日
gitbookio
コミュニティ

build-integration

Build, develop, and publish GitBook integrations — apps that run inside GitBook to add custom blocks, react to events, connect external services via OAuth, and extend the editor. Use this skill whenever a task involves the GitBook integrations platform: scaffolding an integration with the GitBook CLI (gitbook new), writing or editing an integration's code (createIntegration, createComponent, ContentKit TSX), configuring gitbook-manifest.yaml (scopes, blocks, configurations, secrets), building custom editor blocks or link unfurlers, handling GitBook events like spacecontentupdated, setting up an integration's OAuth flow, running gitbook dev, or publishing an integration (private/unlisted/public, marketplace submission). Trigger this even if the user just says they want to 'build an app for GitBook', 'add a custom block', or 'connect to GitBook' without saying the word 'integration'.

導入数
2
GitHub Stars
12
更新日
8月31日
gitbookio
コミュニティ

configure-site

Create and maintain entire GitBook documentation sites end-to-end — design the site structure from source content, scaffold a Git repository in monorepo layout, set up the GitHub/GitLab remote, drive the GitBook API (via its REST API or MCP server) to create the site/sections/spaces, apply branded customization, and hand the user clean instructions for the one UI step (Git Sync wiring) that GitBook does not expose programmatically. Always set up Git Sync at the site level first — mapping every space to a directory in one repo/branch via gitbook-docs.yaml — and only fall back to per-space Git Sync when one space genuinely needs an independent repo or branch. Trigger this skill whenever the user wants to spin up a new GitBook docs site, restructure or extend an existing one, link a site or spaces to a Git repo for sync, change a site's branding (logo, colors, fonts, header/footer), or programmatically manage spaces, sections, or site-spaces. This skill is the orchestration layer; for authoring the markdown content of any individual page it defers to the companion write-docs skill.

導入数
2
GitHub Stars
12
更新日
8月31日
gitbookio
コミュニティ

cr-create

Drive an end-to-end GitBook docs review flow from Claude Code by calling the GitBook REST API directly with curl (no CLI) — create a change request, push content (update an existing page AND create a new page), request reviewers, notify Slack, then pull review comments back in, fix them, re-push, and resolve. This is the authoring-side companion to cr-review (the reviewer side over the same API). Use this whenever someone wants to run a "docs review in GitBook" loop from the terminal/agent against the raw API (curl/HTTP), mentions creating a change request via the API, pushing content into a CR, "pull in the latest comments and fix them," requesting review on docs, or showing engineers how to collaborate on GitBook docs from Claude + Slack without a CLI.

導入数
2
GitHub Stars
12
更新日
8月31日
gitbookio
コミュニティ

cr-review

Review GitBook change requests from Claude Code by calling the GitBook REST API directly with curl (no CLI) — the reviewer-side companion to cr-create (the authoring side over the same API). Discover the change requests that need review (filter by who opened them, by space, or across a whole org), get the GitBook app link to review the diff, summarize what actually changed in a CR, then leave comments and optionally submit a review verdict (approve / request changes). Use this whenever someone wants to review docs change requests over the raw API (curl/HTTP), asks "what CRs are open / waiting on me / opened by ", "show me the change requests in / ", "summarize what changed in this CR", "review this change request", "leave a comment on a CR", or "approve / request changes on a CR". For the authoring side (create a CR, push content, request reviewers, fix comments) over the API, use cr-create instead.

導入数
2
GitHub Stars
12
更新日
8月31日
gitbookio
コミュニティ

write-docs

Write, author, edit, and format GitBook documentation pages in Git-synced repos, IDEs, or any text editor. Use whenever a task involves creating or editing a GitBook markdown page, writing or updating a README.md or SUMMARY.md, inserting a hint, tab, stepper, card, or other GitBook block, configuring page frontmatter or layout options, setting up variables or expressions, or formatting content for GitBook outside the GitBook UI.

導入数
2
GitHub Stars
12
更新日
8月31日
gitbookio
コミュニティ

write-openapi

- Author, configure, structure, and troubleshoot OpenAPI/Swagger API reference documentation in GitBook. Use this whenever a task involves a GitBook OpenAPI block or {% openapi %} block, adding or updating an OpenAPI/Swagger spec in GitBook (by file or URL, via the API, MCP, CLI, or app UI), generating API reference pages from a spec, configuring the interactive "Test it" runner (auth, servers, CORS, proxy), customizing pages with GitBook x- extensions (icons, titles, navigation hierarchy, code samples, enum descriptions), marking operations experimental/deprecated/hidden, or automating spec updates in CI/CD. Trigger even when the user only mentions GitBook plus OpenAPI, puts an x- extension on a spec destined for GitBook, or asks "why isn't my spec loading" or "why doesn't Test it work", without naming this skill.

導入数
2
GitHub Stars
12
更新日
8月31日
inkeep
コミュニティ

consolidate-notes

Promote existing research into a stable-status canonical article under articles/ in a Knowledge Base project (the knowledge-base starter pack). Read when a decision has actually been made and the team wants the source-of-truth written down, or when asked to consolidate, canonicalize, promote research, or supersede an older article. Carries the decision-confirmation gate, the supersedes: chain that keeps the evidence trail intact, and the canonical voice. Does not conduct new research — that is the sibling research-with-sources skill.

導入数
2
GitHub Stars
8
更新日
9月2日
inkeep
コミュニティ

knowledge-base

How to work in a Knowledge Base project (the knowledge-base starter pack). Read when the project has the three-layer source-grounded layout — external-sources/ → research/ → articles/ — or when asked how this project is organized. Carries the layer model, per-folder rules, status flows, and log discipline so this guidance does NOT live inside template bodies or log.md. The three procedures live elsewhere: ingest in the platform open-knowledge skill, research and consolidate as their own sibling skills in this pack. Complements the platform open-knowledge skill; does not replace it.

導入数
2
GitHub Stars
8
更新日
9月2日
inkeep
コミュニティ

research-with-sources

Investigate a topic against preserved sources and write a draft-status research article under research/ in a Knowledge Base project (the knowledge-base starter pack). Read when asked to research a topic, compare options, synthesize sources, gather evidence, or extend an existing research doc. Carries the full procedure: scan existing coverage, agree a research rubric, capture every source verbatim before analyzing, write the article incrementally so a crash never loses work, cite every claim, and link it back into the graph. Does not promote findings to canonical knowledge — that is the sibling consolidate-notes skill, after a decision lands.

導入数
2
GitHub Stars
8
更新日
9月2日
robsonrung
コミュニティ

advanced-react

Plan, implement, or review React component structure, state placement, re-renders, and async behavior using composition first. Use for component design or behavior problems; use react for compiler setup and version-specific APIs.

導入数
2
GitHub Stars
2
更新日
9月8日
robsonrung
コミュニティ

agent-architecture-lens

Review agent control flow, durable state, retries, and recovery. Use when choosing a loop or state graph, or when a tool-calling workflow must survive failures and resume safely.

導入数
2
GitHub Stars
2
更新日
9月8日
robsonrung
コミュニティ

agents-md-craft

Create, audit, or simplify project instruction files such as AGENTS.md and CLAUDE.md. Use to fix instruction drift or separate conditional guidance; use skill-expert for SKILL.md files.

導入数
2
GitHub Stars
2
更新日
9月8日
robsonrung
コミュニティ

architecture-lens

Review code-level coupling, cohesion, dependency direction, and module boundaries. Use when deciding where code belongs or whether to split, merge, or refactor a module; use macro-architecture for system shape.

導入数
2
GitHub Stars
2
更新日
9月8日
robsonrung
コミュニティ

brainstorm

Explore an uncertain idea and recommend whether to build, defer, reduce scope, or reject it. Use for brainstorming or a build decision; use interview-me next to settle requirements.

導入数
2
GitHub Stars
2
更新日
9月8日
robsonrung
コミュニティ

browser-smoke

Smoke-test the routes a branch or PR changes in a real browser. Use when the user asks to smoke-test a branch or PR, test affected pages, or run a diff-scoped browser test. It tests changed routes, not whole-product release QA.

導入数
2
GitHub Stars
2
更新日
9月8日
robsonrung
コミュニティ

capture-learning

Capture a verified, reusable solution in docs/solutions. Use when asked to document a solved problem or when a delivery workflow selects learning capture; use session-handoff for work continuity.

導入数
2
GitHub Stars
2
更新日
9月8日
robsonrung
コミュニティ

claude-runner

Execute prompts using Claude CLI in headless print mode from the current workspace. Use when users explicitly request Claude execution, when a cross-runner workflow selects Claude as the preferred model, or when repo automation needs a Claude CLI seat alongside the other runner seats.

導入数
2
GitHub Stars
2
更新日
9月8日
robsonrung
コミュニティ

clean-code

Refactor existing code with behavior-preserving Clean Code practices. Use for local naming, readability, duplication, or structure problems; use architecture-lens for module boundary decisions.

導入数
2
GitHub Stars
2
更新日
9月8日
robsonrung
コミュニティ

cline-runner

Run a prompt through Cline CLI with structured output. Use when Cline is requested or an approved workflow selects a Cline provider/model route, including the Muse and Minimax seats.

導入数
2
GitHub Stars
2
更新日
9月8日
robsonrung
コミュニティ

cmux-cli

Control cmux workspaces, panels, terminal input, notifications, and sidebar state through its CLI. Use when the user asks to inspect or manage cmux, create or target a workspace or panel, send text or keys, or report task status in cmux.

導入数
2
GitHub Stars
2
更新日
9月8日