본문으로 건너뛰기
cccskills
무료GitHub에 공개

skill-registry

Build and refresh an index of available skills, including when to use each one and its exact file path. Resolve duplicate entries and give agents a current reference after skills are added, removed, moved, or renamed.

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

원문원문 설명 보기

Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path.

설치 방법 보기

이럴 때 유용합니다

  • Refreshing the index after adding or removing skills
  • Resolving duplicate user and project skills
  • Finding exact skill paths before delegating work
  • Saving the skill index to Engram

포함된 파일(1)

  • SKILL.md2.8 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Activation Contract

Use this skill after installing, removing, creating, moving, or renaming skills, or when a delegator needs a fresh skill index.

Hard Rules

  • The registry is an index, not a compiler or summary. SKILL.md remains the source of truth.
  • Do not generate or inject compact rules by default; preserve author intent by passing exact skill paths to subagents.
  • Always write .atl/skill-registry.md, whether or not Engram is available.
  • Save the registry to Engram as topic_key: skill-registry when available, with capture_prompt: false.
  • Generate the registry with gentle-ai skill-registry refresh --cwd <project>: it owns the scan order, deduplication, and the skills it never indexes. Scan by hand only when that command is unavailable.
  • When scanning by hand, skip _shared and skill-registry; deduplicate by skill name, preferring project-level skills over user-level skills.
  • Add .atl/ to .gitignore when possible unless explicitly disabled.

Decision Gates

SituationAction
Same skill exists globally and in projectKeep the project-level skill
Same skill exists in multiple global locationsKeep the first source in scan order
No skills foundWrite an empty registry so agents stop searching blindly
Agent will delegate workSelect matching registry rows and pass their SKILL.md paths

Execution Steps

  1. Run gentle-ai skill-registry refresh --cwd <project> (add --force after skill changes); it writes .atl/skill-registry.md. If it reports the refresh was skipped (not a project), stop: there is no registry to persist. If it succeeds, go to step 4. If it fails, report the error instead of scanning by hand.
  2. Only if the command is unavailable: scan all known user and project skill directories for */SKILL.md, reading frontmatter only as needed to extract name and description trigger text.
  3. Render .atl/skill-registry.md with scanned sources, registry contract, skill name, trigger/description, scope, and exact path.
  4. Persist to Engram when available using title: skill-registry, topic_key: skill-registry, type: config, and capture_prompt: false.
  5. Return the registry path, skill count, cache status, and whether Engram was updated.

Output Contract

Return:

  • Project name and .atl/skill-registry.md path.
  • Number of indexed skills.
  • Whether the cache was hit or regenerated.
  • Any skipped or duplicate skills when relevant.

References

  • docs/skill-style-guide.md — how skills should be authored before indexing.
  • skills/_shared/skill-resolver.md — how delegators use the index.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

branch-pr

무료

Prepare pull requests by checking approved issue links, change-type labels, and required automated checks. Draft the repository’s PR template using observed test results, while leaving commits, pushes, PR creation, and merging under human control.

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

  • Preparing a branch for review
  • Drafting a PR linked to an approved issue
  • Checking required CI before declaring a PR merge-ready
Gentleman-Programming/gentle-ai7.9천2026년 10월 18일 업데이트

Split changes exceeding 400 lines into linked pull requests with clear boundaries and dependencies. Choose a chain structure, keep tests and documentation with each work unit, and document review order, verification plans, and justified size exceptions.

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

  • Splitting a change that exceeds 400 lines
  • Planning PRs that can merge independently
  • Coordinating a feature through a draft tracker PR
Gentleman-Programming/gentle-ai7.9천2026년 10월 18일 업데이트

Structure guides, READMEs, design documents, and pull request descriptions so readers can find answers quickly. Put outcomes first, introduce details gradually, and use examples, tables, and checklists to support understanding and review.

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

  • Reorganizing a long or dense README
  • Writing an onboarding guide for new contributors
  • Making a pull request's review steps clear
Gentleman-Programming/gentle-ai7.9천2026년 10월 18일 업데이트

Draft clear, considerate comments for code reviews, issue replies, and team updates. Put the actionable point first, explain technical reasons when needed, and give a concrete next step while matching the conversation’s language.

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

  • Requesting a code change with a clear reason
  • Replying to a contributor’s issue
  • Writing a brief asynchronous team update
Gentleman-Programming/gentle-ai7.9천2026년 10월 18일 업데이트

Create and verify gentle-ai journeys, which are scripted sequences of product actions. Check their declarations separately from actual execution, review outdated expectations after behavior changes, and record execution results for pull requests.

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

  • Adding a product operation journey
  • Updating expectations after behavior changes
  • Reproducing a bench failure from CI
Gentleman-Programming/gentle-ai7.9천2026년 10월 18일 업데이트

Prepare Gentle AI changes for review by linking approved issues, following branch and commit naming rules, and drafting pull requests with observed test results. Check change size and required automated checks before claiming readiness.

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

  • Preparing a branch for a fix or feature
  • Drafting a pull request linked to an approved issue
  • Organizing test results and reviewer notes
Gentleman-Programming/gentle-ai7.9천2026년 10월 18일 업데이트

Gentleman-Programming의 스킬 모두 보기

이 스킬의 문제 신고