本文へ移動
cccskills
無料GitHub で公開

review

Analyze the available skill set and recommend candidate groups that could be consolidated into sub-skill bundles. Read-only — proposes a plan, does not move files.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Review sub-skills (sub-skill.review)

Analyze the current skill inventory and identify candidate groups that could be consolidated into sub-skill bundles. This sub-skill is read-only: it produces a proposal for the user to review before any file changes are made by sub-skill.consolidate.

When to use

  • The user asks to review, reorganize, or audit the skill inventory.
  • There are many loosely-related skills that might benefit from hierarchical grouping.
  • The user wants to evaluate whether a new skill should be a sub-skill of an existing parent.

Process

  1. List the current inventory. Use the skill registry (or scan the configured skill roots) to get a full list of skill names, descriptions, and source scopes.
  2. Categorize by domain. Group skills by functional domain — e.g. file operations, web tools, collaboration, observability.
  3. Detect coupling. Identify skills that are frequently used together or share similar whenToUse conditions.
  4. Flag granularity issues. Call out skills that are too fine-grained (e.g. one skill per CLI flag) or too broad to land in any single domain.
  5. Propose sub-skill structures. For each candidate group, list:
    • The parent skill name and a one-line description.
    • The children that should move under it.
    • Any documentation, reference, example, asset, or template directories that must move with each child so the final directory layout stays aligned.
    • Whether the parent needs has-sub-skill: true (it does, if children should be discovered).
  6. Output a summary report. Present findings as a concise grouped list with rationale, and stop. Do not edit any file — that's sub-skill.consolidate's job.

Criteria for a good sub-skill grouping

  • Shared context. Children operate within the same domain or workflow.
  • Composable entry point. The parent gives a natural top-level handle; children handle specifics.
  • Shallow nesting. Prefer 2 levels (parent → child). Avoid 3+ unless strictly necessary.
  • Backward compatibility. Existing skill names should ideally remain discoverable.

Example output format

Proposed sub-skill: web-research
  - Parent: web-research (has-sub-skill: true)
  - Children:
    - web-search    → move under web-research/search
    - fetch-url     → move under web-research/fetch
  - Documentation alignment: move each child's references/examples/assets with that child.
  - Rationale: Both deal with online information retrieval and are often chained together.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

日本語の概要は準備中です。原文の説明を表示しています。

PyModel/pythinker-code292026年10月10日 更新

Use when developing in packages/agent-core-v2 (the DI × Scope agent engine) — adding or modifying a domain Service, choosing a LifecycleScope, wiring DI dependencies, splitting a domain across scopes, owning or migrating a config section, gating behavior behind an experimental flag, raising coded errors, working on the permission system, writing DI/Scope tests, porting business logic from agent-core (v1) to v2, triaging a main-branch commit against v2, or exposing a v2 domain over server-v2 while keeping the /api/v1 wire contract compatible with released clients. Self-contained guide organized by development stage (orient → design → implement → test → verify) plus align workflows for v1→v2 migration, main-branch commit triage, and server-v2 wire exposure; each file carries the rules, examples, and red lines for its step.

日本語の概要は準備中です。原文の説明を表示しています。

PyModel/pythinker-code292026年10月10日 更新

Apply an approved sub-skill grouping by moving user-specified skills into a parent bundle, with timestamped backups of every modified directory.

日本語の概要は準備中です。原文の説明を表示しています。

PyModel/pythinker-code292026年10月10日 更新

dogfood

無料

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

日本語の概要は準備中です。原文の説明を表示しています。

PyModel/pythinker-code292026年10月10日 更新

electron

無料

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

日本語の概要は準備中です。原文の説明を表示しています。

PyModel/pythinker-code292026年10月10日 更新

Use when generating changesets in the pythinker-code repository — deciding whether to write one, which package to list, the bump level, the wording, and the confirmation workflow.

日本語の概要は準備中です。原文の説明を表示しています。

PyModel/pythinker-code292026年10月10日 更新

PyModel のスキルをすべて見る

このスキルの問題を報告する