ceo-setup

One-time onboarding for the executive/manager commitment workflow — delegation, meeting prep, decision capture, daily digests. Creates a `commitments` project and two dashboard widgets, then excludes itself until its marker file is deleted.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ceo-setup/SKILL.md

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 highly actionable, clearly sequenced setup skill with strong validation gating; its weakness is progressive disclosure, where bulky widget source files are inlined in SKILL.md rather than split into reference bundle files.

Suggestions

Move the six widget files (manifest.json, index.js, style.css for both widgets) out of SKILL.md into a references/ or assets/ bundle directory, keeping only the memory_write calls that install them — or a pointer — inline.

Inline the shared schema into Step 3 (or a referenced README.md) rather than deferring to another skill's Step 3, so the skill is self-contained at one level of reference depth.

Trim any remaining boilerplate around the tool-call blocks to push conciseness toward the lean anchor.

Dimension	Reasoning	Score
Conciseness	The body is efficient and largely free of over-explanation, but the six verbatim widget files (manifest, index.js, style.css for two widgets) are long inlined blobs that crowd the SKILL.md and would be leaner as separate reference files; this sits between efficient and lean.	3 / 5
Actionability	Every step provides complete, copy-paste-ready tool calls (memory_write, mission_create) with full content payloads and exact cadences/paths, fully executable with no pseudocode or gaps.	5 / 5
Workflow Clarity	An explicit sequential 'Order of operations' (Steps 1-7) plus a prominent upfront validation checkpoint forbidding confirmation until every tool call has succeeded, with a final Step 8 gated on prior success — clear sequence with explicit validation and a feedback gate.	5 / 5
Progressive Disclosure	Structure is clear with labeled steps and one external reference ('see that skill's Step 3'), but the large inlined widget CSS/JS content that clearly belongs in separate bundle files is kept inline in SKILL.md, and no references/ or scripts/ bundle files exist to offload it.	3 / 5
	Total	16 / 20 Passed

Description

75%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 specific, capability-rich description with strong natural trigger vocabulary and a clear niche; its main gap is the absence of an explicit 'Use when...' clause, which keeps completeness and trigger_term_quality just below the top anchor.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when the user identifies as a CEO/manager/executive and needs a delegation, meeting-prep, and decision-capture system set up').

Tighten the capability list into discrete actions (e.g., 'creates a commitments project, installs triage and digest missions, and adds two dashboard widgets') to push specificity toward comprehensive coverage.

Include a distinguishing phrase that separates this one-time setup skill from the ongoing commitment-triage/digest skills to further reduce overlap risk.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('delegation', 'meeting prep', 'decision capture', 'daily digests') and concrete artifacts ('commitments project', 'two dashboard widgets', 'excludes itself'), though a few are described at the level of capabilities rather than discrete operations.	4 / 5
Completeness	Clearly answers 'what' (onboarding workflow that creates a project and two widgets, then self-excludes) and implies 'when' ('One-time onboarding for the executive/manager commitment workflow'), but lacks an explicit 'Use when...' clause tying it to concrete trigger phrases, which would lift it to 5.	4 / 5
Trigger Term Quality	Names several natural terms an executive/manager might say ('delegation', 'meeting prep', 'daily digests', 'commitments'); the 'Use when' framing is absent from the description itself, but the trigger vocabulary is strong with only minor synonyms missing.	4 / 5
Distinctiveness Conflict Risk	The executive/manager commitment-system niche and the self-excluding one-time-setup framing make it largely distinct from general commitment skills, with only minor overlap risk against the sibling commitment-setup skills it references.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nearai/ironclaw
Path: skills/ceo-setup/SKILL.md
Commit: 2831516

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.