CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

issue-solver

Implement a task described by a tracked issue end-to-end -- read the repo, make the code changes, run tests, commit, reconcile with the base branch, and open a pull request. Use when a launcher hands you an issue identifier, title, description, base branch, and feature branch and asks you to deliver the change as a PR. Self-contained: driven entirely by launcher-supplied inputs and a checked-out git clone, with no harness-injected Postgres/Linear/GitHub clients required. Activate for autonomous "solve this issue and open a PR" tasks in any repository, not only kikimora's own subtree.

Quality

83%

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

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.

The body delivers an exemplary executable workflow — sequenced, validated, with error-recovery loops and copy-paste commands. Its weaknesses are length: repeated rules across sections and large policy blocks that a leaner SKILL.md would push into one-level-deep reference files.

Suggestions

Move stable policy blocks (evidence contract, PR title/body format, 'Notes for launchers') into references/ files (e.g. references/evidence.md, references/pr-format.md) and keep one-line pointers in SKILL.md, cutting the main file to a lean overview-plus-procedure.

State each launcher input rule once: the assignee co-author trailer, PR signature, and project-scope rules each appear in the Inputs table, the procedure, and the PR section — consolidate into the Inputs table plus a single use-site mention.

Fix or remove the dangling frontmatter reference ./schemas/output.schema.json, since no schemas/ directory exists in the bundle.

DimensionReasoningScore

Conciseness

Mostly efficient — launcher-specific policy Claude would not know (the backend test override, KIK041/KIK069 rules, tessl verify preconditions, force-with-lease rationale) earns its tokens — but several sections could be tightened: the assignee trailer, PR signature, and project-scope rules are each restated in two or three places, and long policy prose like "Write for humans, not like an LLM" and "Name the invariants" pads the token budget.

3 / 5

Actionability

Fully executable, copy-paste-ready commands throughout: exact git fetch/merge/push --force-with-lease with branch-name validation, gh pr list/create with flags, commit message templates, a concrete pr-body.md content spec, and a complete worked PR-title example. Conditional steps (comment reading, tracker CLI) state their conditions and fallbacks explicitly.

5 / 5

Workflow Clarity

Ten clearly sequenced steps with explicit validation checkpoints and feedback loops: run tests and fix failures (step 4), fix tessl verify failures before committing (step 5), conflict-resolution sub-steps (step 7), push-before-verify with a failure stop rule (step 8), and "Do not open the PR until git status is clean and the re-run passes" (step 9) — including a turn-budget self-correction rule.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), so this ~510-line SKILL.md is monolithic: clearly sectioned with headers, but content that belongs in separate reference files — the evidence contract, PR body/title format, and "Notes for launchers" — is inlined, and the frontmatter's $ref to ./schemas/output.schema.json points at a nonexistent file.

3 / 5

Total

16

/

20

Passed

Description

83%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 description: it names concrete end-to-end actions, states explicit 'use when' triggers with a natural trigger phrase, and carves out a distinctive autonomous-dispatch niche. The only deductions are an incidental second-person pronoun (per the rubric's voice rule) and a few missing natural synonyms like 'ticket' or 'fix'.

DimensionReasoningScore

Specificity

The description lists six concrete end-to-end actions ("read the repo, make the code changes, run tests, commit, reconcile with the base branch, and open a pull request") which fits the 5 anchor, but the rubric's explicit voice rule penalizes second person — "Use when a launcher hands you an issue identifier" — so specificity drops by 1 to 4.

4 / 5

Completeness

Both questions are explicitly answered: the 'what' is the full action list, and the 'when' appears twice with concrete triggers ("Use when a launcher hands you an issue identifier, title, description, base branch, and feature branch" and "Activate for autonomous 'solve this issue and open a PR' tasks in any repository").

5 / 5

Trigger Term Quality

Good natural keyword coverage: "issue", "pull request", "base branch", "feature branch", "commit", and a quoted natural trigger phrase ("solve this issue and open a PR"). A few natural synonyms users might say are missing (e.g. "ticket", "bug", "fix this issue"), which keeps it at 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The launcher-driven, autonomous issue-to-PR framing is a clear niche with a distinct trigger, but the broadened scope "in any repository, not only kikimora's own subtree" leaves minor overlap risk with general coding/commit/PR skills, so it sits just below the 5 anchor.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (528 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

drew-tessl/linear-factory-testing

Path

plugins/issue-solver/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.