CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bazinga

Invoke this skill when the user asks you to develop a feature back-to-back, with all the trimmings. This skill defines a full feature development workflow that includes code reviews, branch management, and ends in a fully fleshed-out PR.

Quality

76%

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 ./.agents/skills/bazinga/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

The content is a well-engineered workflow skill: explicit sequencing, strong validation gates with SHA pinning and verdict invalidation, feedback loops for review and CI failures, and concrete CLI commands. Its only weaknesses are light chatty padding and a couple of thin sections (Simplification Pass, deferred review guidance).

DimensionReasoningScore

Conciseness

The body is lean, instruction-only content with no explanations of concepts Claude already knows; only minor chatty connectives ("Hi.", "It is imperative to note that", "Now it's time to review") could be trimmed.

4 / 5

Actionability

Concrete commands appear throughout ("gh pr checks <pr> --json name,state,link", "gh run view <run-id> --job <job-id> --log-failed", "fix/...", "feat/..." branch patterns) alongside specific directives like recording the reviewed HEAD SHA and writing a failure/interleaving matrix. Minor gaps: the Simplification Pass and the adversarial-review step defer detail to other skills.

4 / 5

Workflow Clarity

The workflow opens with an explicit ordered step list, defines loops with exit conditions ("repeat... until the code review comes up empty"), and includes validation checkpoints with feedback loops — the Planning Checkpoint, the SHA-pinned Final Head Gate with verdict invalidation on HEAD mutation, and the CI watch-and-fix loop — plus a checkbox checklist tracked in the context file.

5 / 5

Progressive Disclosure

No bundle files exist and the ~109-line body is organized into clear, well-sequenced sections for a single coherent workflow. It exceeds the 50-line simple-skill threshold and the detailed Watch CI guidance could arguably live in a reference file, so it falls just short of a 5.

4 / 5

Total

17

/

20

Passed

Description

58%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.

The description correctly answers both what the skill does and when to invoke it, but undersells the workflow's actual scope and leans on idiosyncratic trigger phrasing ("back-to-back, with all the trimmings") that users are unlikely to produce naturally. It is serviceable but sits in the middle of the rubric range.

Suggestions

Replace the idiosyncratic trigger phrase "develop a feature back-to-back, with all the trimmings" with natural variations users would actually say, e.g. "Use when the user asks to develop or implement a feature, build out a change end-to-end, or take a change all the way to a reviewed PR".

Broaden the "what" to reflect the full workflow — mention planning with a user checkpoint, test/review iteration loops, CI monitoring, and a final report — instead of only "code reviews, branch management".

Drop the fluff phrase "with all the trimmings" and add distinguishing keywords (PR, CI, code review loop) to reduce overlap with generic development and code-review skills.

DimensionReasoningScore

Specificity

The description names a few concrete actions ("code reviews, branch management, and ends in a fully fleshed-out PR"), but coverage gaps are major rather than minor — planning, testing, CI monitoring, and the checkpoint gates that dominate the body are unmentioned, and "with all the trimmings" is pure fluff.

3 / 5

Completeness

Both "what" ("full feature development workflow that includes code reviews, branch management, and ends in a fully fleshed-out PR") and an explicit "when" clause ("Invoke this skill when the user asks you to develop a feature") are present. Not 5 because the trigger is narrower than the skill's actual scope (the body also covers making a change) and lacks concrete trigger-phrase variations.

4 / 5

Trigger Term Quality

"develop a feature" is a natural phrase, but "back-to-back, with all the trimmings" is idiosyncratic phrasing users are unlikely to say, and common variations like "implement/build a feature", "make a change", or "open a PR" are missing.

3 / 5

Distinctiveness Conflict Risk

"Develop a feature... code reviews... PR" carves out a recognizable niche but sits in a broad trigger domain with real overlap risk against code-review, commit-message, and general dev-workflow skills.

3 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

chattocorp/chatto

Path

.agents/skills/bazinga/SKILL.md

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.