CtrlK
BlogDocsLog inGet started
Tessl Logo

devtu-github

GitHub workflow for ToolUniverse - push code safely by moving temp files, activating pre-commit hooks, running tests, and cleaning staged files. Use when pushing to GitHub, fixing CI failures, or cleaning up before commits.

66

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/devtu-github/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with a clear, well-validated multi-step workflow and recovery loops. Conciseness and progressive disclosure are the weak spots: some over-explanation and all content inlined into one file rather than split across references.

Suggestions

Move the 'Common Test Failure Patterns' catalog and 'Pre-Commit Hook Configuration' into separate reference files linked from SKILL.md to improve progressive disclosure.

Trim explanatory prose around ruff/hook purposes that Claude already knows; keep just the commands and the red-flag lists.

Reduce the verbose excluded-files tables to a compact bullet list or a single glob-pattern reference.

DimensionReasoningScore

Conciseness

Mostly efficient with executable commands and tables, but some sections over-explain known concepts (e.g., explaining ruff/linting purposes, restating hook checks) and the long file-pattern tables pad the body.

3 / 5

Actionability

Fully executable copy-paste-ready bash and python snippets covering cleanup, hooks, tests, commit, rebase, and push, with concrete diagnostic fixes for each failure pattern.

5 / 5

Workflow Clarity

Clear four-phase sequence with explicit validation checkpoints (git status red flags, hook verification, test pass gate, mergeable check) and a feedback loop for rebase conflicts and test failures.

5 / 5

Progressive Disclosure

Well-organized with clear sections, but it is a single monolithic SKILL.md with no external reference files; the failure-pattern catalog and pre-commit config are inlined rather than split out.

3 / 5

Total

16

/

20

Passed

Description

81%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concrete description that answers both what and when with natural trigger phrases. Minor gaps in synonym coverage and slight overlap risk with general commit skills keep it just below top marks.

Suggestions

Add common synonyms users might say, such as 'commits', 'merge conflicts', or 'pull requests', to broaden trigger matching.

Sharpen the 'cleaning up before commits' trigger to emphasize the pre-push safety context to reduce overlap with generic commit helpers.

DimensionReasoningScore

Specificity

Lists several concrete actions ('moving temp files, activating pre-commit hooks, running tests, and cleaning staged files'), but coverage of the full push workflow is slightly more than minor gaps.

4 / 5

Completeness

Clearly states both what it does (push code safely via cleanup, hooks, tests, staged-file cleaning) and when to use it ('Use when pushing to GitHub, fixing CI failures, or cleaning up before commits').

5 / 5

Trigger Term Quality

Includes natural user phrases ('pushing to GitHub', 'fixing CI failures', 'cleaning up before commits'); missing common synonyms like 'commit', 'merge conflicts', or 'pull request'.

4 / 5

Distinctiveness Conflict Risk

The GitHub-push niche is fairly distinct with concrete triggers, but 'cleaning up before commits' has minor overlap risk with general git/commit skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mims-harvard/ToolUniverse
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.