1# Contributing to Agent Skills for Context Engineering
2 
3Thank you for your interest in contributing to this collection of Agent Skills for Context Engineering. This document provides guidelines and instructions for contributing.
4 
5## How to Contribute
6 
7### Reporting Issues
8 
9If you find errors, unclear explanations, or missing topics, please open an issue with:
10- A clear description of the problem
11- The skill and section where the issue was found
12- Suggested improvements if you have them
13 
14### Submitting Changes
15 
16For substantive changes, please:
17 
181. Fork the repository
192. Create a feature branch for your changes
203. Make changes following the skill template structure
214. Ensure SKILL.md files remain under 500 lines
225. Add references or scripts as appropriate
236. Submit a pull request with a clear description of changes
24 
25### Adding New Skills
26 
27When adding new skills:
28 
291. Use the template in `template/SKILL.md`
302. Follow naming conventions (lowercase with hyphens)
313. Include both SKILL.md and appropriate references/scripts
324. Update the root README.md to include the new skill
335. Ensure content is platform-agnostic (works across Cursor, Claude Code, etc.)
34 
35## Skill Structure Requirements
36 
37Each skill must include:
38 
39- YAML frontmatter with `name` and `description` fields
40- Clear sections with logical organization
41- Practical examples where appropriate
42- Integration notes linking to related skills
43 
44Optional additions:
45 
46- `references/` directory with additional documentation
47- `scripts/` directory with executable examples
48- Multiple markdown files for complex skills
49 
50## Content Guidelines
51 
52### Writing Style
53 
54- Be direct and precise
55- Use technical terminology appropriately
56- Include specific guidance, not vague recommendations
57- Provide concrete examples
58- Point out complexity and trade-offs
59 
60### Avoiding Platform Specificity
61 
62Skills should work across agent platforms. Avoid:
63- Platform-specific tool names without abstraction
64- Vendor-locked examples
65- Features specific to one agent product
66 
67### Keeping Skills Focused
68 
69Each skill should have a single focus. If a topic grows too large, consider splitting into multiple skills with clear dependencies.
70 
71## Code of Conduct
72 
73This project follows a professional, technical collaboration model. Be respectful of different perspectives and focus on improving the collective knowledge base.
74 
75## Questions
76 
77For questions about contributing, please open an issue for discussion.
78 
79