スキルレーダー · GITHUB

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

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

掲載範囲: 検証済み
Skills: 10,772
リポジトリ: 1711
最終同期: 2026/09/23

10,772 Skills

automate-project-maintenance

Orchestrate repository maintenance. Use when Codex needs one entry point to refresh tests, docs, README, and GitHub metadata.

導入数: 1
GitHub Stars: 0
更新日: 5月11日

Rewrite Python docs and docstrings from source code. Use when Codex needs to refresh docs, add executable doctest examples, update Google-style docstrings, or regenerate zensical/mkdocstrings reference pages.

導入数: 1
GitHub Stars: 0
更新日: 5月11日

write-conventional-commit

Generate exactly one high-quality Conventional Commit message from the current Git diff. Use when Codex needs to inspect staged changes, summarize the dominant intent, and return only the final commit message with no analysis or extra text.

導入数: 1
GitHub Stars: 0
更新日: 5月11日

write-root-readme

Write or rewrite the repo-root README.md.

導入数: 1
GitHub Stars: 0
更新日: 5月11日

architecture-review

审视代码库中有证据支撑的架构改进机会，并输出一份中文交接报告。适用于指定的子系统、痛点、即将开发的功能或近期热点。不得修改产品代码。

導入数: 1
GitHub Stars: 0
更新日: 9月20日

grill-me

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any "grill" trigger phrases.

導入数: 1
GitHub Stars: 0
更新日: 9月20日

project-docs

为长期维护的仓库建立项目级基础文档。先只读审计并建议应创建的文档，待用户确认后只补齐缺失文件，不改写已有文档。

導入数: 1
GitHub Stars: 0
更新日: 9月20日

prototype

Build a throwaway prototype to answer a specific design, state model, or UI exploration question. Use when evaluating whether an interface feels right, exploring UI concepts, or testing logic before committing to a full spec, even if the user says \"mock this up\". Do NOT use for production implementation.

導入数: 1
GitHub Stars: 0
更新日: 9月20日

tdd

以测试先行的方式实现规则明确的功能、修复可复现的缺陷，或为重构补足行为保护。仅在需求和验收行为已明确时主动使用，不用于探索性原型或尚未定型的设计。

導入数: 1
GitHub Stars: 0
更新日: 9月20日

teach

Teach a technical concept interactively using the workspace as an active learning lab with durable learning records. Use when the user asks to understand a codebase concept, learn a language feature, explore design patterns, or practice coding skills, even if they say \"explain how this works to me\". Do NOT use for silent autonomous code generation.

導入数: 1
GitHub Stars: 0
更新日: 9月20日

to-spec

Turn the current, confirmed grill-me feature discussion into a task spec under docs/specs: no interview, just synthesis of what you have already discussed.

導入数: 1
GitHub Stars: 0
更新日: 9月20日

code-review

Review code changes (diffs, commits, branches, PRs) for bugs, structure issues, and unintentional behavior changes. Use when the user asks to 'review this code', 'review my changes', 'review this PR', 'check my diff', 'look over this commit', 'code review', or any request involving evaluating code quality of recent changes. Also trigger when the user pastes a diff or mentions reviewing a branch, PR number, or commit hash. Even vague requests like 'does this look right?' or 'anything wrong with my changes?' should trigger this skill.

導入数: 1
GitHub Stars: 0
更新日: 9月2日

commit

Creates git commits that match the repository's history instead of defaulting to conventional commits. Use this skill whenever the user wants to record changes in git, asks for a commit message, or indicates that the work is ready to wrap up.

導入数: 1
GitHub Stars: 0
更新日: 9月2日

flatpak-flathub

Creates complete, Flathub-ready Flatpak packages: manifest, MetaInfo, desktop file, README, and PR description. Use whenever the user is packaging or submitting an app to Flatpak/Flathub: writing a manifest (app-id, finish-args, sdk-extensions, buildsystem), generating offline dependency sources (cargo-sources.json, generated-sources.json, python3-modules.json), writing AppStream metainfo.xml, setting sandbox permissions, fixing Flathub linter errors, choosing a runtime (GNOME 49 / KDE 6.9 / Freedesktop 25.08), or preparing a Flathub submission PR. Covers Rust/Cargo, Python/Meson, Node/Electron/pnpm, Go, .NET, GTK, Qt, CMake. Use for finish-args, OARS ratings, branding colors, flatpak-builder vs org.flatpak.Builder, Electron BaseApp/zypak, extra-data (Spotify, Slack, Zoom, VS Code), repackaging from Snap/AppImage/.deb for Flathub. Do not use for creating native snap/AppImage/deb/AUR packages, general Linux distro questions, or "flatpak vs X" comparisons.

導入数: 1
GitHub Stars: 0
更新日: 9月2日

flatpak-sdk-extension-maintenance

Maintains versioned Flatpak SDK and SDK-extension repositories by propagating a dependency or release update from a reference pull request across every maintained branch/ runtime branch. Use this whenever a user asks to update, backport, cherry-pick, synchronize, or roll out changes across Freedesktop, GNOME, KDE, or other Flatpak SDK and extension branches, especially when branches are several releases behind or conflicts must preserve runtime-specific manifest settings. Prepares and validates one update branch per target, then requires approval before pushing or opening GitHub pull requests. Do not use for ordinary Flatpak application updates, creating a new Flatpak package, or general application-code backports.

導入数: 1
GitHub Stars: 0
更新日: 9月2日

qlcplus

Helps with QLC+ workspace files (.qxw), scenes, chasers, sequences, collections, EFX, RGB matrices, fixture definitions (.qxf), Virtual Console, and timing calculations. Use for creating or editing QLC+ shows, debugging timing and crossfades, generating fixture definitions, configuring plugins, repairing corrupt workspaces, or troubleshooting HTP and LTP conflicts. Also trigger for SpeedModes, FadeIn, Hold, Duration, FixtureVal, RunOrder, and QLC+ function types. Do not trigger for general DMX hardware questions without QLC+ context, fixture buying advice, DAW-only questions, or custom protocol implementations.

導入数: 1
GitHub Stars: 0
更新日: 9月2日

adr-shape

Write and review architecture decision records in one shape — a lead paragraph naming what the ADR closes, numbered decisions with their reasoning inline, a verdict on every considered option, consequences that separate better from worse and list what was deliberately left open, a status that is a condition when it needs to be, and corrections as dated updates. Ships the template and a lint for the mechanical parts. Use when an ADR is to be written from a resolved discussion or an existing one reviewed against the shape.

導入数: 1
GitHub Stars: 0
更新日: 9月20日

guidance-tiers

Establish frozen and living documentation tiers in a repository — a never-edited reference directory, living docs (a vocabulary file, an architecture document, ADRs), a precedence rule in the guidance file, and a check script run in CI that fails when the rules are broken. Use when a project starts from a design document (a brief, a spec, a contract) that agents must treat as authoritative while the project's current understanding diverges from it on purpose.

導入数: 1
GitHub Stars: 0
更新日: 9月20日

hidden-verify

Run, screenshot, or verify a change in a desktop application without a window ever appearing — the project skill for launching the application, which run looks for first. An environment contract the shell reads at start makes a run render the window unseen, capture a PNG after a delay, quit, and keep every piece of non-project state in a scratch directory. Use when asked to run the application or confirm a change works in it, when a change needs proof for a PR, or when the application lacks the hook and is about to be verified beside a person.

導入数: 1
GitHub Stars: 0
更新日: 9月20日

land-ticket

Merge a ticket's green PR, close the ticket, open the public-site issue when the change moved the page, and report the new frontier.

導入数: 1
GitHub Stars: 0
更新日: 9月20日

pin-prototypes

Draft and run the prompt set that takes a project's brief through an HTML-exporting design tool the human drives. Use when a project has a brief and is about to prompt a design tool for its surfaces, when a design session has degraded and needs splitting, or when a surface is about to be implemented from a pinned prototype — or has none.

導入数: 1
GitHub Stars: 0
更新日: 9月20日

10 ファイル

詳細を見る →