Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →devtu-github
GitHub workflow for ToolUniverse - push code safely by moving temp files, activating pre-commit hooks, running tests, and cleaning staged files.
Passed 9 of 23 test cases with the skill, and 0 of 23 without it.
and 8 more in the full report
9 fixed0 passed either way14 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
What exact command line should I execute to run the local pytest suite with fast-failing on first error, short tracebacks, and quiet output?
| Checked | Without skill | With skill |
|---|---|---|
| Provides the command python -m pytest tests/ -x --tb=short -q. | Missed | Passed |
The instructions your model reads when the skill loads.
Safely push ToolUniverse code to GitHub by enforcing pre-push cleanup, pre-commit hooks, and test validation.
When the user wants to push code, fix CI, or prepare a commit, follow this workflow:
# Move session markdown files to temp_docs_and_tests/
for f in $(ls *.md 2>/dev/null | grep -v README.md | grep -v CHANGELOG.md | grep -v LICENSE.md); do
mv "$f" temp_docs_and_tests/
done
# Move root-level test scripts to temp_docs_and_tests/
for f in $(ls test_*.py 2>/dev/null); do
mv "$f" temp_docs_and_tests/
done
git status --short
Red flags - these should NEVER be staged:
*_SUMMARY.md, *_REPORT.md, SESSION_*.md in roottest_*.py in root (these are ad-hoc scripts, not real tests).env or credential filestemp_docs_and_tests/ contentstest cases passed, vs 0 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.