CtrlK
BlogDocsLog inGet started
Tessl Logo

goal

Set an explicit objective, success criteria, and stopping conditions for the current OpenScience session.

66

Quality

80%

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 ./backend/cli/skills/other/goal/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 well-structured, concise instruction-only skill with concrete actionable guidance, a sequenced workflow, and explicit verification checkpoints. With no bundle files needed, progressive disclosure is satisfied by its clean section organization.

DimensionReasoningScore

Conciseness

The body is lean — tight bullet lists and short sections with no padding or explanation of concepts Claude already knows, matching the anchor for lean, token-efficient content.

3 / 3

Actionability

As an instruction-only skill it gives concrete, specific guidance — verification types ("tests, builds, local runs, screenshots, logs, or provider/API checks") and persistence targets ("project files, commits, PRs, or Atlas records") — which is actionable without code.

3 / 3

Workflow Clarity

Execution is a clearly numbered 1–5 sequence with an explicit verification checkpoint in Completion ("verify each success criterion with fresh evidence") and a blocker-reporting feedback loop.

3 / 3

Progressive Disclosure

At ~25 lines with no need for external references, the well-organized Contract/Execution/Completion sections meet the simple-skill allowance for a full score without bundle files.

3 / 3

Total

12

/

12

Passed

Description

60%

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 specific and lists concrete deliverables, but it lacks an explicit use-trigger clause and relies on terms a user might not naturally say, capping completeness and trigger quality at 2. Distinctiveness is moderate thanks to the OpenScience scoping but still somewhat generic.

Suggestions

Add an explicit "Use when..." trigger clause (e.g., "Use when the user asks to define a goal, set success criteria, or establish stopping conditions for a session") to satisfy both completeness and trigger coverage.

Include natural user phrasings such as "set a goal", "define done", or "plan a multi-step task" alongside "OpenScience session" to improve trigger term quality.

Sharpen distinctiveness by tying the skill specifically to long-running, multi-turn OpenScience work rather than generic objective-setting, so it is less likely to collide with general planning skills.

DimensionReasoningScore

Specificity

Names multiple concrete deliverables to set — "an explicit objective, success criteria, and stopping conditions" — rather than vague language, matching the anchor that lists several specific actions.

3 / 3

Completeness

It clearly states what the skill does but never states when to use it; per the guidelines, a missing "Use when..." clause caps completeness at 2.

2 / 3

Trigger Term Quality

Relevant keywords exist ("objective", "success criteria", "stopping conditions") but there is no "Use when..." clause and common user phrasings like "set a goal" are missing, so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The "OpenScience session" scoping adds a niche, but objective/success-criteria setting is generic planning that could overlap with other workflow or planning skills.

2 / 3

Total

9

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
synthetic-sciences/openscience
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.