사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/jrgilbertson/the-rookery --skill creating-portable-skills시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Creating Portable Skills
Produce an installable package that does the user's reusable job and follows the Agent Skills specification. Add behavioral evals when observed failures warrant them under the host's evaluation policy.
For a read-only audit, apply references/review-checklist.md and return prioritized findings with file evidence and a verdict. For authorized creation, revision, or migration, use the workflow below. Existing authorization and the host project's constraints carry forward.
Author the package
Ground the skill in the user's intent, existing package, representative inputs and outputs, and corrections from real work. Identify the outcome and hard constraints that make completion acceptable. Check the host's contribution rules, discovery path, and existing owners before adding a workflow or helper.
For a new skill, use assets/skill-template.md. For a revision, the last commit can preserve the prior version. For a migration, revise a copy and preserve the source. Read references/portability.md when choosing frontmatter, bundling dependencies, or removing harness-specific assumptions.
Keep one instruction set for the job. Separate changing facts from reusable instructions when that lets the next update change one source. Put conditional guidance in references/, copied outputs in assets/, and deterministic helpers in scripts/ when an existing mechanism cannot meet the requirement. Bundle everything the package needs, or declare its actual environment dependencies.
Apply references/review-checklist.md while drafting. Preserve user authority, exact formats, privacy requirements, and fragile operation order; leave reasoning and implementation choices open.
Validate and evaluate
Use skills-ref validate <skill-directory> from an available trusted install. If it is unavailable, check the specification's frontmatter rules, name-directory match, body, and local resource links directly, and record the limitation. Exercise bundled helpers with realistic inputs in disposable storage outside the host project; preserve existing inputs and outputs.
Package checks, helper tests, and applicable authorized smoke checks run for every package. For behavioral evaluation, follow references/evaluation.md.
Deliver
Check the final package's local links, dependencies, host conventions, and applicable evaluation evidence. Report the package location, observed checks, and anything unverified. For public migrations, replace private examples with synthetic inputs that preserve the behavior and difficulty being tested, and inspect the whole copy for leaks. Keep answers and grading material outside the runtime instructions. Follow the host's release and installation process.
Sources
The Agent Skills specification owns the package format. references/evaluation.md owns evaluation and names the upstream workflows it uses.

