context-window-to-skill
- Repo stars 98
- License MIT
- Author updated Live
- Author repo .context
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- 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 special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: context-window-to-skill
description: Takes the active conversation as reference to understand how a skill can be created, with all th…
category: other
runtime: no special runtime
---
# context-window-to-skill output preview
## PART A: Task fit
- Use case: Takes the active conversation as reference to understand how a skill can be created, with all the lessons learned from the users need in the conversation. 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 ….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Decide Fit First / Design Intent / How To Use It” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Takes the active conversation as reference to understand how a skill can be created, with all the lessons learned from the users need in the conversation. 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 …”.
- **02** When the source has headings, the agent prioritizes “Decide Fit First / Design Intent / How To Use It” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Decide Fit First / Design Intent / How To Use It”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: context-window-to-skill
description: Takes the active conversation as reference to understand how a skill can be created, with all th…
category: other
source: forefy/.context
---
# context-window-to-skill
## When to use
- Takes the active conversation as reference to understand how a skill can be created, with all the lessons learned from…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Decide Fit First / Design Intent / How To Use It” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "context-window-to-skill" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Decide Fit First / Design Intent / How To Use It
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} 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:
- Analyze conversation and understand fully what the user tried to achieve
- Analyze where were the pitfalls, user frustrations, and what pre-information would have made the results quicker to get with the most quality
- Print to the user 10 (or more) top items you think are the core points to base the new skill upon
- Consult with the user if questions still remain
- 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)
Decide Fit First
Design Intent
How To Use It
Boundaries And Review