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

writing-skills

Creates or improves an Agent Skill by defining a precise trigger boundary, concise procedural instructions, progressive-disclosure references, deterministic helpers, routing evals, and validation evidence. Use when authoring or reviewing SKILL.md, skill metadata, bundled references, or skill packaging. Not for ordinary project documentation or application code.

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

thiientv/godmode
설치 방법 보기

포함된 파일(3)

  • SKILL.md2.9 KB
  • references/evaluation-loop.md890 B
  • references/skill-checklist.md970 B

SKILL.md(원문)

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

Writing Skills

Write a skill for another agent to use under pressure. Context is a shared budget, so every paragraph must earn its place.

Design the boundary

  1. Collect concrete prompts that should and should not activate the skill.
  2. Name the responsibility in plain language and use a short verb-led name.
  3. Put all activation conditions in frontmatter description; the body loads only after activation.
  4. Keep SKILL.md procedural and under 500 lines.
  5. Move detailed rules, variants, schemas, and examples into one-level-deep references/ files.
  6. Add a script only for deterministic repeated work, with --help and tests.

Use skill-checklist.md before opening a PR.

Write and test

  • Use Agent Skills-compatible name and description frontmatter.
  • State when to use, when not to use, safety boundaries, workflow, handoffs, and completion evidence.
  • Avoid copying a reference repository's text, names, examples, or scripts; rewrite principles and record provenance.
  • Add at least three positive and two negative routing cases, including close neighbors that must not activate.
  • Create two or three realistic behavior cases with observable outputs and edge conditions before expanding the suite.
  • Run each case in a fresh context with the candidate skill and with no skill or a frozen previous version. Keep prompts, fixtures, model settings, and output locations identical.
  • Capture artifacts, public trace/tool summaries, duration, and usage. Grade deterministic assertions first and use blinded rubric or human review for judgment-heavy output.
  • Optimize description triggering on a training set and choose the final result by a held-out validation set; do not paste missed query keywords into the description until fixtures pass by accident.
  • Run the repository validator and at least one realistic forward test for a behavior-changing skill.

Descriptions should be specific enough to distinguish neighboring skills, but not so broad that every task activates the skill.

Use agent-evaluation for the baseline/candidate result format and regression analysis. Read evaluation-loop.md before claiming that a skill improves agent behavior.

Completion condition

A skill is ready when its trigger boundary is understandable, its body is actionable, its links and helpers work, its routing cases generalize, and a realistic isolated comparison produces better evidence than the baseline without an unacceptable cost or protected-metric regression.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

agent-evaluation

무료

Designs and runs reproducible evaluations for AI agents, prompts, tools, skills, and model-backed workflows using realistic datasets, isolated baselines, objective assertions, rubric grading, trajectory analysis, cost/latency tracking, and regression comparison. Use when measuring agent quality, optimizing skill triggering, comparing prompts or models, or gating an AI feature release. Not for ordinary deterministic unit tests.

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

thiientv/godmode992026년 8월 26일 업데이트

api-and-interface-design

무료

Designs or reviews HTTP, REST, GraphQL, RPC, CLI, webhook, event, and service interfaces with explicit inputs, outputs, errors, compatibility, idempotency, pagination, authentication, versioning, and observability. Use when introducing or changing an API or cross-component contract. Not for internal implementation details with no boundary or for debugging one API failure; use root-cause-debugging there.

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

thiientv/godmode992026년 8월 26일 업데이트

architecture-review

무료

Reviews an existing codebase for structural friction, unclear ownership, leaky or shallow interfaces, excessive coupling, misplaced state, poor testability, and risky dependency direction, then prioritizes evidence-backed improvement candidates. Use for architecture audits, modularization, modernization, or recurring cross-cutting change pain. Not for designing one new interface, simplifying a local function, or fixing a reproduced bug.

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

thiientv/godmode992026년 8월 26일 업데이트

behavior-validation

무료

Validates a running application, CLI, API, service, or generated artifact as a user or operator against a prewritten observable behavior contract while remaining source-blind. Use for acceptance checks, runtime proof, anti-fake probes, release smoke tests, or an independent companion to code review. Not for source-quality findings, root-cause diagnosis, or visual design judgment outside the contract.

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

thiientv/godmode992026년 8월 26일 업데이트

branch-integration

무료

Closes a completed development branch by checking the final diff and proof, presenting merge, pull-request, keep, or discard options, and cleaning up only after the user or repository workflow chooses a path. Use when feature work is complete and the branch must be integrated or retired. Not for claiming a feature is complete before verification.

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

thiientv/godmode992026년 8월 26일 업데이트

browser-testing

무료

Tests a real web user flow with a browser by asserting semantic behavior, network and loading states, keyboard access, responsive layouts, and stable visual evidence. Use for browser bugs, end-to-end UI behavior, responsive or accessibility checks, and screenshot baselines. Not for static source review without a browser or for backend-only tests.

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

thiientv/godmode992026년 8월 26일 업데이트

thiientv의 스킬 모두 보기

이 스킬의 문제 신고