context window to skill
- Repo stars 98
- License MIT
- Author repo .context
- Domain
- Other
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 94 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @forefy · MIT
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Use Case:
User had finished working on his feature or task successfully, but had to tweak lots of stuff in the behavior of the agent prior to completion - we now want to create a skill that in the next time will make this task a breeze
Steps:
1. Analyze conversation and understand fully what the user tried to achieve
2. Analyze where were the pitfalls, user frustrations, and what pre-information would have made the results quicker to get with the most quality
3. Print to the user 10 (or more) top items you think are the core points to base the new skill upon
4. Consult with the user if questions still remain
5. Create a skill and place it on the ~/.claude/skills/ directory. comply to agent skill format and [https://code.claude.com/docs/en/skills](https://code.claude.com/docs/en/skills)
Results:
- Working new skill, that next time would do the job much better with all the tweaks needed to perfect it based on learned conversation and observation
- New skill should be reusable (e.g. think fixes also for future usecases other than the single one the user encountered) Sections and files
Listed in source order.
sections -> → →
terms -> Steps: 1.
files/cmd -> .claude/skills · code.claude.com/docs/en/skills
body sha256 -> 4e2285975660
User had finished working on his feature or task successfully, but had to tweak lots of stuff in the behavior of the agent prior to completion - we now want to create a skill that in the next time will make this task a breeze
Steps: 1. Analyze conversation and understand fully what the user tried to achieve 2. Analyze where were the pitfalls, user frustrations, and what pre-information would have made the results quicker to get with the most quality 3. Print to the user 10 (or more) top items you think are the core points to base the new skill upon 4. Consult with the user if questions still remain 5. Create a skill and place it on the ~/.claude/skills/ directory. comply to agent skill format and https://code.claude.com/docs/en/skills
Results: - Working new skill, that next time would do the job much better with all the tweaks needed to perfect it based on learned conversation and observation - New skill should be reusable (e.g. think fixes also for future usecases other than the single one the user encountered)