update skill-creator: delete eval workspace before committing
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
45a294cdc8
commit
98fc73b948
1 changed files with 1 additions and 0 deletions
|
|
@ -484,6 +484,7 @@ Repeating one more time the core loop here for emphasis:
|
||||||
- Run quantitative evals
|
- Run quantitative evals
|
||||||
- Repeat until you and the user are satisfied
|
- Repeat until you and the user are satisfied
|
||||||
- Package the final skill and return it to the user.
|
- Package the final skill and return it to the user.
|
||||||
|
- **Clean up the eval workspace** before committing. Delete the `<skill-name>-workspace/` directory (e.g., `rm -rf skills/update-skill-index-workspace/`) — it contains only temporary test fixtures, transcripts, and grading files that shouldn't be committed.
|
||||||
- **Commit and push** any changes made to the `skills/` folder. After creating or updating a skill in the `skills/` directory, run `git add` and `git commit` with a descriptive commit message (e.g., "create new skill: meeting-notes" or "update skill: daily-briefing — add calendar dependency"), then `git push`. This keeps the skills repo in sync.
|
- **Commit and push** any changes made to the `skills/` folder. After creating or updating a skill in the `skills/` directory, run `git add` and `git commit` with a descriptive commit message (e.g., "create new skill: meeting-notes" or "update skill: daily-briefing — add calendar dependency"), then `git push`. This keeps the skills repo in sync.
|
||||||
|
|
||||||
Please add steps to your TodoList, if you have such a thing, to make sure you don't forget. If you're in Cowork, please specifically put "Create evals JSON and run `eval-viewer/generate_review.py` so human can review test cases" in your TodoList to make sure it happens.
|
Please add steps to your TodoList, if you have such a thing, to make sure you don't forget. If you're in Cowork, please specifically put "Create evals JSON and run `eval-viewer/generate_review.py` so human can review test cases" in your TodoList to make sure it happens.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue