CtrlK
BlogDocsLog inGet started
Tessl Logo

write-oep

Draft an Open SWE Enhancement Proposal using the repository's OEP process and template. Use when the user asks to create, write, or propose an OEP or invokes /write-oep.

66

Quality

78%

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/write-oep/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, mostly lean instruction-only process skill with concrete file paths, an explicit verification checklist, and clear sequencing. The main gaps are an implicit rather than explicit validate-retry loop and no worked example of a completed OEP.

Suggestions

Make the validation feedback loop explicit in section 5 (e.g., 'If git diff --check or lint fails: fix the issue and re-run before opening the PR').

Add a short inline example of one filled-in template section (e.g., a sample Motivation or Proposed Decision paragraph) to lift actionability.

Trim redundant 'do not' scoping clauses that repeat the same boundary across sections 2 and 4.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence without explaining basic concepts, though a few 'do not' clauses and repeated scoping reminders could be trimmed slightly.

4 / 5

Actionability

Provides concrete, executable guidance—specific paths ('oeps/TEMPLATE.md', 'oeps/NNNN-short-title.md') and a real command ('git diff --check')—with minor gaps such as no example of a filled-in OEP section.

4 / 5

Workflow Clarity

A clear five-step sequence with a verification checklist in section 5 (verify links, metadata, numbering; run git diff --check and lint), though the validate->fix->retry feedback loop is implicit rather than explicit.

4 / 5

Progressive Disclosure

Well-organized into numbered sections with no nested references and clear in-situ structure; at ~75 lines it slightly exceeds the under-50-line simple-skill threshold that would permit a 5 without external file splits.

4 / 5

Total

16

/

20

Passed

Description

82%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, well-scoped description that clearly states both capability and trigger conditions with natural user phrasing and a slash command. The only weakness is modest action specificity, listing essentially one verb (draft) backed by the process/template mechanism.

DimensionReasoningScore

Specificity

Names the domain ('Open SWE Enhancement Proposal') and 1-2 concrete actions ('Draft ... using the repository's OEP process and template'), but coverage of distinct actions is minimal rather than comprehensive.

3 / 5

Completeness

Explicitly answers both 'what' (draft an OEP using the process and template) and 'when' ('Use when the user asks to create, write, or propose an OEP or invokes /write-oep') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage with synonyms ('create, write, or propose an OEP') plus the explicit '/write-oep' slash command, missing only a few variant phrasings.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (OEP proposal drafting) with distinct triggers tied to a named repo process, minimizing overlap with other skills.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
langchain-ai/open-swe
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.