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

consolidate

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

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.9 KB

SKILL.md(原文)

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

Consolidate sub-skills (sub-skill.consolidate)

Execute the reorganization by moving user-specified skills into a parent bundle, forming a sub-skill hierarchy.

When to use

  • The user has approved a grouping proposal (typically from sub-skill.review) and wants to apply it.
  • Migrating standalone skills into a new or existing parent bundle.

Process

  1. Confirm the plan. Restate which skills will move and where, and ask the user to confirm before making any file changes.
  2. Back up every original skill directory. Before moving anything, create a timestamped backup of each skill directory that will be modified.
    • For a skill at <root>/<skill-name>/SKILL.md, back up the entire <skill-name> directory:
      cp -r <skill-name> "<skill-name>.$(date +%Y%m%d-%H%M%S).bak"
      
    • Keep all backups; never overwrite an existing backup file.
  3. Create or update the parent bundle.
    • If the parent does not exist, create <parent-name>/SKILL.md with has-sub-skill: true in the frontmatter.
    • If the parent already exists, ensure its frontmatter includes has-sub-skill: true.
  4. Move child skills into the parent. Move each child skill's entire directory under the parent bundle.
    • Example: web-search/ → web-research/web-search/
  5. Keep documentation directory alignment. When moving documentation, references, examples, assets, or other payload directories, align them with the new skill directory layout.
    • Preserve relative links from SKILL.md to files such as references/, assets/, examples/, or templates.
    • If a child skill moves from <root>/<child>/ to <root>/<parent>/<child>/, its documentation payload should move with that child unless the approved plan says otherwise.
    • Do not leave documentation in the old location or merge unrelated documentation directories together.
  6. Verify the result. List the new directory structure and confirm each moved skill still has a valid SKILL.md with required frontmatter (name and description). Check documentation directory alignment and relative links after the move.
  7. Report the change. Summarize what was moved, the new structure, any documentation directories that moved, and where backups are located.

Don'ts

  • Never move skills without backing up first.
  • Never overwrite an existing backup — always use a fresh timestamped suffix.
  • Don't drop frontmatter or payload files during the move; the entire directory must be preserved.
  • Don't break documentation directory alignment — references, assets, examples, and templates must stay aligned with the skill directory that uses them.
  • Don't create deeply nested hierarchies (3+ levels) unless the user explicitly requests it.

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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日 更新

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日 更新

gen-docs

無料

Update Pythinker Code CLI user documentation after meaningful code changes that affect product behavior or user experience.

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

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

PyModel のスキルをすべて見る

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