CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

build-from-issue

Plan and implement work described in a GitHub issue, including verification, documentation, and a PR that closes the issue.

Quality

81%

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

92%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 an exemplar of lean, operational skill writing: a clearly phased workflow with concrete commands, exact output formats, explicit pre-push validation, and well-signaled one-level-deep references to repo-level guidance. The only mild weakness is actionability, where a few execution details (commit format, verification specifics) are deferred to other documents rather than shown.

DimensionReasoningScore

Conciseness

The body is lean and dense — e.g. "Implement the smallest coherent change that fulfills the acceptance criteria" — with no explanations of concepts Claude already knows and no padded sections. Every directive carries operational weight, matching the 5 anchor; the 4 anchor's "minor instances of over-explanation" are absent.

5 / 5

Actionability

Concrete, executable guidance is present throughout: the exact command `gh issue view <id> --json number,title,body,state,labels,comments,assignees`, the exact comment markers `> **🏗️ build-plan**` / `> **🏗️ build-from-issue-agent**`, `mise run rust:deny:policy`, and `Closes #<id>` in the PR's Related Issue section. Minor gaps keep it below 5: some steps defer execution specifics elsewhere ("follow the verification guidance in `CONTRIBUTING.md`", "use a signed-off Conventional Commit" without showing the format).

4 / 5

Workflow Clarity

The Inspect → Plan → Implement phases are clearly sequenced with explicit validation checkpoints and error-recovery paths: "Before pushing, apply the contributor access and issue acceptance check in `create-github-pr`. If blocked, preserve local work and report the reason", "Stop only when information needed to do the work is actually unavailable", selection of format/lint/type checks and E2E lanes, and a feedback loop for unanswered plan-comment feedback. This matches the 5 anchor's explicit validation and error-recovery criteria.

5 / 5

Progressive Disclosure

The body is a ~30-line overview organized into three clear sections, with details appropriately deferred one level deep and well-signaled: "Label Discovery in `CONTRIBUTING.md`", "Branch Names in `CONTRIBUTING.md`", "the verification guidance in `CONTRIBUTING.md`", and the linked [crypto architecture](../../../crates/openshell-crypto/CRYPTO.md). No bundle files exist under references/, scripts/, or assets/, nothing is inlined that belongs in a separate file, and no references nest deeper than one level — matching the 5 anchor.

5 / 5

Total

19

/

20

Passed

Description

66%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 is concise, concrete, and clearly third-person, communicating a specific issue-to-PR workflow with several named actions. Its main weakness is the absence of any explicit "Use when..." trigger clause, which caps completeness and leaves natural trigger variations uncovered.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to plan, implement, or close a specific GitHub issue with a PR."

Include natural trigger variations users would actually say — "implement this issue", "build from issue #N", "open a PR that closes the issue" — to improve trigger-term coverage.

Briefly state the boundary (e.g., defer to security-issue skills for vulnerabilities) in the description to sharpen distinctiveness against sibling repo skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Plan and implement", "verification, documentation, and a PR that closes the issue" — anchored to the GitHub-issue domain. It falls short of the 5 anchor because "work" is generic and the coverage of the workflow's actions, while good, is not comprehensive.

4 / 5

Completeness

The "what" is clearly answered ("Plan and implement work described in a GitHub issue, including verification, documentation, and a PR that closes the issue"), but there is no "Use when..." clause or equivalent explicit trigger guidance — the "when" is only weakly implied. Per the judging guidelines, a missing "Use when" clause caps completeness at 3; it is not 4 because the trigger guidance is absent entirely rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural terms a user would say are present — "GitHub issue", "PR", "closes the issue", "verification" — giving good keyword coverage. It misses common variations and synonyms such as "ticket", "bug", "feature request", or "fix/close an issue", so it does not reach the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The issue-anchored implementation scope is a distinct niche unlikely to trigger for unrelated skills. There is minor overlap risk with closely related git/PR or issue-triage skills, matching the 4 anchor rather than the 5 anchor's "minimal conflict risk".

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

NVIDIA/OpenShell

Path

.agents/skills/build-from-issue/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.