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

skill-improver

Audit existing SKILL.md files for clear activation conditions, usable instructions, and defined outputs. Get prioritized findings and specific improvements, with changes applied only when requested and the author's intent preserved.

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

원문원문 설명 보기

Trigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills.

설치 방법 보기

이럴 때 유용합니다

  • Audit existing skills for quality issues
  • Clarify when a skill should activate
  • Move lengthy examples into supporting files
  • Apply improvements while preserving essential rules

포함된 파일(2)

  • SKILL.md3.0 KB
  • references/skill-style-guide.md3.3 KB

SKILL.md(원문)

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

Activation Contract

Use this skill when asked to audit, refactor, normalize, or improve existing SKILL.md files. Use skill-creator instead when creating a brand-new skill from a reusable pattern.

Hard Rules

  • Treat docs/skill-style-guide.md as the normative style contract when it exists.
  • For installed global skills, use references/skill-style-guide.md as the bundled local copy when docs/skill-style-guide.md is unavailable.
  • Treat SKILL.md as the source of truth; preserve author intent, critical rules, activation semantics, and output requirements.
  • Use .atl/skill-registry.md as an index of skill names, triggers, scopes, and exact paths; do not expect generated summaries.
  • Default to audit-only. Modify files only when the user explicitly asks to apply improvements.
  • Never delete meaningful content silently; move long explanation, examples, templates, or schemas into local references/ or assets/.
  • Do not invent triggers, policies, or domain rules. Mark ambiguous cases for human review.

Decision Gates

SituationAction
Missing or invalid frontmatterFix name, quoted one-line description, license, and metadata
Skill reads like tutorial docsConvert to runtime instructions and move background to references/
Body exceeds budgetPreserve rules, move examples/background to supporting files
Branching logic hidden in proseConvert to a compact decision table
Rules conflict or intent is unclearReport the issue; do not rewrite that rule automatically

Execution Steps

  1. Read docs/skill-style-guide.md; if unavailable, read references/skill-style-guide.md; if neither exists, enforce the core LLM-first structure: frontmatter, Activation Contract, Hard Rules, Decision Gates, Execution Steps, Output Contract, References.
  2. Read .atl/skill-registry.md; use listed paths to select skills. If missing, scan known skill directories for */SKILL.md.
  3. For each selected skill, audit metadata, trigger clarity, section order, body budget, actionability, decision gates, output contract, and local references.
  4. Return an audit report grouped by skill with severity and exact proposed changes.
  5. In apply mode, edit only safe issues, preserve content, create supporting files when needed, then rerun or request gentle-ai skill-registry refresh.

Output Contract

Return:

  • Skills audited and paths used.
  • Issues found, grouped by severity.
  • Files changed, if apply mode was requested.
  • Registry refresh recommendation when skill metadata or paths changed.
  • Ambiguities that need human review.

References

  • docs/skill-style-guide.md — normative LLM-first skill style guide for this repo.
  • references/skill-style-guide.md — bundled local copy for installed global skills when the repo doc is unavailable.

리뷰

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

댓글

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

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

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. 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의 스킬 모두 보기

이 스킬의 문제 신고