본문으로 건너뛰기
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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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월 18일 업데이트

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월 18일 업데이트

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월 18일 업데이트

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월 18일 업데이트

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월 18일 업데이트

gen-docs

무료

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

PyModel/pythinker-code292026년 10월 18일 업데이트

PyModel의 스킬 모두 보기

이 스킬의 문제 신고