CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

integration-orchestrator

Generate a phased delivery orchestration plan for creative-direction-driven work: which skills run when, what locks at which gate, how handoffs occur, and how the cadence implements in the team's tools (Jira, Linear, Notion, Figma, GitHub) with AI agents via MCP and CLI. A temporal map of phases, lock points, handoff specs, gate definitions, and QA verification gates. Distinct from `creative-brief` (static project brief) and `creative-direction` (aesthetic direction). Triggers on integration orchestrator, delivery cadence, project orchestration, when does the brief lock, how to phase creative direction, design-development handoff, QA gate, agent-driven QA, and when a creative-direction project is starting, mid-flight with broken cadence, or integrating AI agents into PM workflow. Does NOT fire for project scoping (use `creative-brief`), aesthetic direction (use `creative-direction`), or general project management without a creative-direction throughline.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 well-structured instruction skill: genuinely non-obvious framework content, concrete gate criteria and cadence tables, and exemplary one-level-deep progressive disclosure backed by seven real reference files. The main gaps are rhetorical padding in the opening sections and an implicit rather than explicit workflow sequence with no plan-validation step.

Suggestions

Cut the rhetorical intro and the 'What this skill is' section down to a few lines — they restate the description; lead instead with 'Required inputs' followed by an explicit step sequence (inputs, 7 considerations, cadence template, output format).

State the execution order explicitly as a numbered workflow, and add a final validation step for the produced plan (e.g., verify every gate has measurable pass criteria and every lock point names its artifact and re-review scope).

Inline one short copy-paste example per platform (a Jira Epic field set, a Linear project/label setup, or a Playwright QA-gate invocation) so the body delivers on its 'MCP commands for setup' promise without forcing a reference-file hop.

DimensionReasoningScore

Conciseness

The framework, cadences, and failure patterns are dense and skill-specific, but the two-paragraph rhetorical intro, the 'What this skill is' section restating the description, and aphorisms ('Gates that are not measurable become political') are tighten-able padding. Anchor 3 (mostly efficient, some unnecessary explanation) — not 2, since nothing explains concepts Claude already knows; not 4, since several passages could be cut without loss.

3 / 5

Actionability

Concrete throughout for an instruction-only skill: 7 cadences with week ranges, measurable gate criteria ('Playwright critical-flow suite green, console error count at or below baseline'), the Todo/In Progress/Waiting/Blocked/Done taxonomy with agent permissions, an 8-section output format, and a 7-item required-inputs list. Anchor 4 (mostly executable, minor gaps) — not 5, because the promised 'ticket templates the PM can paste into Jira' and MCP commands appear only via reference pointers, not inline.

4 / 5

Workflow Clarity

The procedure (gather inputs, apply the 7 considerations, select a cadence template, produce the 8-section plan) is implicit in the section ordering rather than stated as a sequence, and there is no validation of the produced plan (no check that gates are measurable or all output sections are populated). Anchor 3 (sequence present, checkpoints implicit) — not 4, which requires most checkpoints explicitly present.

3 / 5

Progressive Disclosure

The body is an overview that summarizes each cadence and defers detail; a dedicated 'Reference files' section lists all 7 files with one-line descriptions; every referenced path resolves to a real, substantive file (verified against the bundle listing); references are exactly one level deep with no nested 'see X' chains. Matches anchor 5.

5 / 5

Total

15

/

20

Passed

Description

95%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 highly effective description: concrete capability list, comprehensive natural trigger phrases including question forms and scenario states, and explicit boundaries against the two sibling skills. The only weaknesses are mild redundancy between the first two sentences and omission of the concrete deliverable filename.

DimensionReasoningScore

Specificity

Lists multiple concrete outputs ('a temporal map of phases, lock points, handoff specs, gate definitions, and QA verification gates', tool-specific implementation for Jira, Linear, Notion, Figma, GitHub with MCP and CLI), but the second sentence largely restates the first and the concrete deliverable (ORCHESTRATION.md) is never named. Matches anchor 4 (several specific actions, minor gaps) rather than 5's comprehensive non-redundant coverage.

4 / 5

Completeness

Explicitly answers what ('Generate a phased delivery orchestration plan...'), when ('Triggers on... when a creative-direction project is starting, mid-flight with broken cadence, or integrating AI agents into PM workflow'), and when-not ('Does NOT fire for project scoping...'). Matches the anchor-5 example's what+when+trigger structure exactly.

5 / 5

Trigger Term Quality

Triggers cover natural phrases users would actually say, including question forms ('when does the brief lock'), compound requests ('design-development handoff', 'agent-driven QA'), and scenario states ('mid-flight with broken cadence'). Comprehensive natural-term coverage matching anchor 5; not 4, since no common variation is obviously missing.

5 / 5

Distinctiveness Conflict Risk

'Distinct from `creative-brief` (static project brief) and `creative-direction` (aesthetic direction)' plus explicit negative triggers ('Does NOT fire for project scoping, aesthetic direction, or general project management') carve out a clear niche. Minimal conflict risk, matching anchor 5.

5 / 5

Total

19

/

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.

Validation — 15 / 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

rampstackco/claude-skills

Path

skills/integration-orchestrator/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.