CtrlK
BlogDocsLog inGet started
Tessl Logo

engagement-startup

Mandatory first-turn startup procedure — checks for existing engagements, resume/new selection, workspace initialization.

60

Quality

70%

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 ./packages/decepticon/decepticon/skills/standard/decepticon/engagement-startup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 lean, well-structured, and actionable with a clear multi-step workflow and confirmation gates. Minor gaps are in executable code formality and explicit validate-fix-retry feedback loops.

Suggestions

Add an explicit validation checkpoint after binding the workspace (e.g., confirm load_opplan succeeded before reading planning docs).

Show the exact expected return shape of load_opplan so the resume-vs-new branch decision is unambiguous.

Consider a short 'Expected output' note for the delegation to Soundwave so the orchestrator can verify regeneration occurred.

DimensionReasoningScore

Conciseness

The body is lean and directive with no padding or explanation of concepts Claude already knows; every line earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Provides concrete tool calls (load_opplan, read_file, task) and specific paths, but they are orchestration-style invocations rather than copy-paste runnable code, matching 'mostly executable guidance; minor gaps'.

4 / 5

Workflow Clarity

Clear sequence (Step 1, 2, 3A/3B branching) with confirmation checkpoints and a delegation path for missing docs, matching 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references and no unnecessary bundle files; fits 'good structure; most content appropriately placed; minor organization gaps'.

4 / 5

Total

17

/

20

Passed

Description

58%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 specific and distinct but lacks an explicit 'Use when...' trigger clause, capping completeness. Trigger terms are present but not comprehensive in natural phrasings.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke this skill (e.g., 'Use at agent startup, first message, or session start').

Include natural synonyms a user might say, such as 'session start', 'new engagement', and 'resume session'.

Slightly expand the action list to cover the full scope (e.g., 'loads planning state, resumes or builds the OPPLAN').

DimensionReasoningScore

Specificity

Names three concrete actions ('checks for existing engagements, resume/new selection, workspace initialization'), fitting the 'several specific actions; minor gaps' anchor better than the 1-2 action anchor at 3.

4 / 5

Completeness

The 'what' is clear (startup procedure with three checks) but there is no explicit 'Use when...' trigger clause, and the guideline caps completeness at 3 for a missing explicit trigger clause.

3 / 5

Trigger Term Quality

Includes relevant terms like 'first-turn startup' and 'engagements' but lacks common synonyms or natural phrasings a user would say, matching 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

Targets a specific niche (engagement startup bootstrap) with low overlap risk against other skills, fitting 'mostly distinct; minor overlap risk'.

4 / 5

Total

14

/

20

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
PurpleAILAB/Decepticon
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.