CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-ideas

Generate ideas in one shot using creative sampling

Quality

66%

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 ./antigravity/skills/create-ideas/SKILL.md

The canonical home for this skill is create-ideas in NeoLabHQ/context-engineering-kit

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 is a lean, concrete prompt with explicit numeric constraints, and its size and structure suit a simple single-purpose skill. Its main defect is the leftover template placeholder "[full distribution / tails of the distribution]", which leaves the sampling strategy ambiguous, plus minor role-play padding. Fixing the placeholder and stating the distribution rule directly would make it fully executable.

Suggestions

Resolve the bracketed placeholder into a definite instruction, e.g. "Sample the first 3 responses from the high-probability region of the distribution and the last 3 from the tails."

Drop the "You are a helpful assistant." role-play line and politeness filler ("please") to tighten token efficiency.

Add a one-line worked example of a single list item (text + probability) so the expected output format is unambiguous.

DimensionReasoningScore

Conciseness

The body is about 10 lines and states its constraints tersely ("over 0.80", "less than 0.10"), but "You are a helpful assistant." and repeated "please" are padding Claude does not need. This is anchor 4 ("Efficient; minor instances of over-explanation that could be trimmed") rather than 5, where every token would earn its place.

4 / 5

Actionability

The instructions include concrete specifics (6 items, text plus numeric probability, explicit probability bounds), but the unresolved placeholder "[full distribution / tails of the distribution]" leaves a key parameter as an unchosen either/or — it reads like an unfinished template. That gap fits anchor 3 ("Some concrete guidance but incomplete ... missing key details") better than 4, where guidance would be mostly executable with only minor gaps.

3 / 5

Workflow Clarity

This is a simple, single-action, non-destructive skill, so the simple-skill exception applies and no multi-step sequence or validation loop is required. The action is clear, but the bracketed distribution choice and the slightly tangled "first 3 / last 3" phrasing introduce minor ambiguity, keeping it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files, and needs no external references; a single heading over a short, well-ordered body is appropriate structure. Per the rubric's simple-skill note this earns anchor 5 (clear, well-organized, nothing that should be split out).

5 / 5

Total

16

/

20

Passed

Description

45%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 short and readable but under-specified: it names a single generic action with no trigger guidance, no concrete output description, and no natural synonyms like "brainstorm". It communicates a rough purpose but would not reliably fire for the right requests or distinguish itself from similar ideation skills.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to brainstorm, generate candidate responses, or explore diverse options for a question."

Make the "what" concrete: state the actual output (e.g. "Generate 6 candidate responses with probabilities, sampling both high-probability answers and diverse low-probability alternatives").

Include natural synonyms and phrasings users would say (brainstorm, propose alternatives, suggest options) to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

The description gives one generic action — "Generate ideas" — plus the method phrase "using creative sampling", without saying what kind of ideas or what the output looks like. This matches anchor 2 ("Names the domain but actions are minimal or generic") and falls short of anchor 3, which expects 1-2 concrete, comprehensible actions; "creative sampling" is closer to jargon than a concrete capability.

2 / 5

Completeness

There is a partial "what" (generate ideas via creative sampling) but no "when" clause at all, which per the judging guidelines caps completeness at 3. It is not a 4 because a "Use when..." trigger is entirely absent rather than merely imprecise, and not a 2 because the "what" half, while thin, is stated.

3 / 5

Trigger Term Quality

"Generate ideas" is a phrase a user might naturally say, but "in one shot" and "creative sampling" are technique jargon rather than user vocabulary, and common variations like "brainstorm", "come up with options", or "suggest alternatives" are absent. This fits anchor 3 ("Some relevant keywords but missing common variations or synonyms") rather than 4, where coverage would be genuinely good.

3 / 5

Distinctiveness Conflict Risk

"Creative sampling" and "one shot" give the skill a somewhat distinct identity, but "generate ideas" is broad enough to overlap with general brainstorming or ideation skills. Anchor 3 ("Somewhat specific but could still overlap with similar skills") is the best fit; it lacks the clear, distinct trigger set of anchor 4.

3 / 5

Total

11

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NeoLabHQ/context-engineering-kit

Path

antigravity/skills/create-ideas/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.