CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

intake

Use when Creative Production is explicitly invoked or mentioned without a concrete request, when the user asks what Creative Production can do, or when the user wants help getting started without enough context to choose a workflow.

60

Quality

76%

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 ./plugins/creative-production/skills/intake/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 an exemplar of lean, actionable instruction with a clearly sequenced workflow and strong guardrails, assuming Claude's intelligence throughout. The only gap is the absence of an explicit error-recovery loop, which is not strictly required for this non-destructive open-and-hand-off flow.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no concept explanations, no padding; every line is actionable instruction, matching the anchor for lean, efficient content where every token earns its place.

5 / 5

Actionability

It provides a copy-paste-ready JSON call to creative_production_board, named downstream tools (begin_generation, complete_generation, produce), and explicit do/don't rules, fully covering the common cases.

5 / 5

Workflow Clarity

A clear six-step sequence carries explicit checkpoints (preserve boardId, 'exactly once', 'never call open again'), but there is no error-recovery feedback loop; it is non-destructive so the destructive-cap does not apply, placing it just below the validation/checklist anchor.

4 / 5

Progressive Disclosure

At under 50 lines with no need for external references and well-organized sections (Intake, Workflow, Exit), the content meets the simple-skill exception that allows a 5 on well-organized sections alone.

5 / 5

Total

19

/

20

Passed

Description

47%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 excels at trigger guidance with natural, multi-clause Use-when phrasing, but it omits any statement of what the skill actually does, leaving completeness and capability specificity weak. It is reasonably distinct thanks to the named-app anchoring.

Suggestions

Add a brief 'what' clause stating the skill's concrete action, e.g. 'Opens the Creative Production app in its zero state. Use when ...'.

Name one or two concrete capabilities (e.g. 'renders the starter grid and hands off to produce') to lift specificity above the domain-only anchor.

Include a synonym or two for the trigger (e.g. 'not sure where to start' or 'blank slate') to broaden natural keyword coverage beyond the proper noun.

DimensionReasoningScore

Specificity

The description names the domain ("Creative Production", "getting started", "choose a workflow") but states no concrete actions or capabilities, matching the anchor for naming the domain with minimal/generic actions rather than listing 1-2 concrete actions.

2 / 5

Completeness

It supplies a strong, explicit "when" (three Use-when clauses) but never states what the skill does, fitting the anchor where only "when" is present without "what".

2 / 5

Trigger Term Quality

Phrases like "asks what Creative Production can do", "wants help getting started", and "without enough context to choose a workflow" are natural user language with good coverage, though they are tethered to one proper noun and miss common synonyms.

4 / 5

Distinctiveness Conflict Risk

Anchoring to the named Creative Production app and the narrow no-brief entry niche makes it mostly distinct, with only minor overlap risk against the sibling produce skill.

4 / 5

Total

12

/

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

openai/plugins

Path

plugins/creative-production/skills/intake/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.