사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/devhive1/devhive-cli --skill skill-authoring시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Skill Authoring
Create skills to save reusable knowledge, procedures, and workflows that persist across sessions. Skills are instructions for future versions of yourself—write them as if teaching a fresh instance how to handle a task.
When to Use
- User asks to "create a skill" or "teach you how to do X"
- User wants to save instructions for repeated future use
- A workflow should be reusable across sessions
How to Create a Skill
- Choose a skill name (lowercase, hyphens only, e.g.,
code-review) - Write the SKILL.md file to
.agents/skills/SKILLNAME/SKILL.md
SKILL.md Format
markdown
---
name: skill-name
description: What this skill does. When to use it.
---
# Skill Title
Instructions, examples, and workflows go here.Frontmatter Requirements
name: Max 64 chars, lowercase letters/numbers/hyphens onlydescription: Max 1024 chars, include WHAT it does and WHEN to use it
Writing Tips
- Be concise: Only include info you don't already know
- Match specificity to fragility: Exact commands for fragile ops, general guidance for flexible tasks
- Include examples: Input/output pairs help with output quality
- Keep under 500 lines: For longer skills, reference separate files
Skill Locations
- `.agents/skills/` - User and agent-editable skills. Create new skills here. These can be freely modified, updated, and deleted.
- `~/.local/skills/` - Replit-provided skills. These are read-only and managed by the platform.
Key Considerations
- Description is critical for discovery: The description determines when you'll use this skill in the future. Be specific about triggers:
- Bad:
description: Processes documents(too vague) - Good:
description: Extracts text and images from PDF files. Use when the user asks to read, parse, or convert PDF documents. - Collaborate with the user: Ask what they want included. Don't guess—the user knows what's important to them
- Include project-specific context: File paths, naming conventions, API endpoints, preferred libraries—things unique to this user's workflow
- Use separate files for large content: Organize reference material in folders (e.g.,
.agents/skills/SKILLNAME/reference/api.md) and link to it from SKILL.md - Skills can be updated: Skills in
.agents/skills/are mutable. Update them as you discover better patterns—don't treat them as permanent. Iterate as the user's needs evolve - Skills can reference other skills: A skill can invoke or build upon other skills. Use this to compose complex workflows from simpler building blocks
Complete Example
markdown
---
name: pr-review
description: Reviews pull requests for code quality and security. Use when the user asks to review a PR or check code changes.
---
# PR Review
## Process
1. Read the PR description and linked issues
2. Review each file for issues
3. Check for test coverage
4. Look for security vulnerabilities
5. Summarize findings with line references
## What to Check
- Logic errors and edge cases
- Security issues (injection, XSS, auth bypass)
- Performance concerns
- Missing error handling
## Output Format
\`\`\`markdown
## Summary
[1-2 sentence overview]
## Issues Found
- **[severity]** file:line - description
## Verdict
[Approve / Request Changes / Comment]
\`\`\`
