CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

factory-wrapup

Prepare an approved ticket for human submission by updating durable knowledge, summarizing scope and verification, teaching material flows with progressive visuals, and providing the merge handoff. Use only after review approval. Unless codeHost.pullRequests is false, commit the approved work, push the ticket branch, and create or update the pull request. It never merges.

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally actionable, tightly written operational skill with a clearly sequenced workflow, strong validation checkpoints, and safety rails around git operations. References are well structured and conditionally loaded. The only improvements available are minor tightening of the longest paragraphs and resolving the one cross-bundle reference.

DimensionReasoningScore

Conciseness

The body is dense and purely operational with no explanations of concepts Claude already knows, but a few spots could be trimmed — the very long pull-request-title paragraph and the repeated "Never use git add -A" prohibition — matching the 4 anchor ("efficient; minor instances of over-explanation that could be trimmed") rather than the 5 anchor where every token earns its place.

4 / 5

Actionability

Guidance is fully executable throughout: exact shell commands with placeholders (git status --porcelain, explicit-path git add, gh pr list/edit/create with heredoc, the ff-only merge sequence), plus precise conventions for tracker refs (#42 vs ENG-42) and single-quote escaping — copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

The multi-step process is clearly sequenced (readiness check → knowledge updates → issue checklist → diff annotation → handoff → PR → merge commands → output) with explicit validation checkpoints and feedback loops: stop-and-return gating on failed checks, "The last command must print nothing" after commit, failure handling that reports the exact failing command and falls back to printed merge commands, and hard rails (never amend/rebase/force-push, never merge).

5 / 5

Progressive Disclosure

The overview is well organized with clearly signaled, one-level-deep references loaded conditionally at the point of need (visual-explanations.md for 3+ moving parts, usage-table.md, panes-handoff.md, output.md), and all four referenced files exist. Minor gaps keep it below 5: the cross-skill link ../factory-plan/references/context.md does not resolve within this bundle, and the dense PR-title and merge-command details are fully inlined.

4 / 5

Total

18

/

20

Passed

Description

92%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 highly specific, complete, and well-bounded description for a pipeline-internal wrap-up skill. It clearly states what it does, when to use it, its conditional PR behavior, and its hard boundary of never merging. The only weakness is trigger phrasing that leans on internal jargon rather than natural user terms.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the whole workflow — "updating durable knowledge, summarizing scope and verification, teaching material flows with progressive visuals, and providing the merge handoff" plus "commit the approved work, push the ticket branch, and create or update the pull request" — which is comprehensive coverage for its domain, exceeding the 4 anchor's "minor gaps in coverage".

5 / 5

Completeness

It explicitly answers "what" (prepare an approved ticket for human submission via the listed actions) and "when" ("Use only after review approval"), reinforced by a concrete condition ("Unless codeHost.pullRequests is false, commit... push... create or update the pull request") and a boundary ("It never merges"), matching the 5 anchor rather than the 4 anchor where "when" could be more explicit.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("approved ticket", "pull request", "merge handoff", "commit", "push") but it mixes in internal jargon ("durable knowledge", "codeHost.pullRequests") and lacks common synonyms or variations, so it falls just short of the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — post-review ticket wrap-up and human merge handoff — with explicit boundaries ("Use only after review approval", "It never merges") that minimize overlap with neighboring plan/work/review skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

geut/factory-skills

Path

skills/factory-wrapup/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.