CtrlK
BlogDocsLog inGet started
Tessl Logo

finishing-a-development-branch

Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.

57

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agency/plugins/nori/skills/finishing-a-development-branch/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 body is a strong, executable workflow: clearly numbered steps, per-language commands, hard validation gates on tests and CI, and explicit error-recovery loops. Weaknesses are minor — a commandless type-checking step, an abstract demo-link step, and a little promotional padding.

DimensionReasoningScore

Conciseness

The body is command-first and lean, but contains minor trimmable content: the twice-repeated "merely a way to get a fresh pair of eyes on the code" asides and the promotional "Share Nori with your team" link in the PR template.

4 / 5

Actionability

Concrete executable guidance throughout — per-language detection and fix commands (jq over package.json, cargo clippy, ruff, golangci-lint), a complete gh pr create template, and a CI retry loop. Gaps: step 5 (type checking) provides no commands at all, and step 12's localhost demo instruction is abstract.

4 / 5

Workflow Clarity

A clearly sequenced 12-step workflow with explicit validation gates: a hard stop on test failures ("Cannot proceed until tests pass"), a CI feedback loop with retry (sleep 60 && gh pr checks), conflict recovery routing back to the merge step, a main-branch safety check, and an upfront TodoWrite checklist.

5 / 5

Progressive Disclosure

A single well-organized SKILL.md with no nested references or buried paths, and the inline per-language command matrices are compact enough to justify staying in the main file. Slightly below the top anchor: no section headers, and at ~110 lines the language-specific command blocks could plausibly live in reference files.

4 / 5

Total

17

/

20

Passed

Description

48%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 nails the "when" with an explicit trigger clause, but provides almost no "what" — the skill's multi-step verification, review, and PR workflow is invisible from it. Second-person phrasing and missing synonyms ("pull request", "merge") further weaken it.

Suggestions

List the skill's concrete capabilities in third person (e.g., "Runs the project test suite, applies formatters and linters, performs self-review, pushes the branch, creates a PR, and verifies CI") so the "what" is explicit.

Add natural trigger synonyms such as "pull request", "open a PR", "merge", and "finish/ship the branch" to broaden keyword coverage.

Keep the "Use when..." clause but pair it with the capability list so both "what" and "when" are concretely answered.

DimensionReasoningScore

Specificity

The only concrete capability named is "create a PR"; phrases like "completed some feature implementation" and "have written passing tests" describe preconditions rather than what the skill does (run tests, lint, typecheck, review, push, verify CI). The second-person phrasing ("you have completed... you are ready") incurs the rubric's -1 specificity penalty.

2 / 5

Completeness

It has a strong explicit "Use this when..." trigger clause, but the "what" is only weakly implied by the embedded "ready to create a PR" — none of the skill's actual workflow steps (test verification, formatting/lint/typecheck, self-review, CI verification) are surfaced in the description.

3 / 5

Trigger Term Quality

Natural terms like "PR", "passing tests", and "feature implementation" are present, but common variations and synonyms are missing — "pull request" is never spelled out, and "merge", "finish the branch", or "ship this" are absent.

3 / 5

Distinctiveness Conflict Risk

The trigger condition (feature complete, passing tests, ready to create a PR) carves out a fairly distinct niche with clear triggers; only minor overlap risk with code-review or PR-review skills that also trigger on "PR".

4 / 5

Total

12

/

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
microsoft/FluidFramework
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.