create-playbook-component

Use when: adding a new playbook automation component, implementing a PlaybookComponent interface, or registering a new playbook step

Quality

82%

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

Quality

Content

86%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 tight, well-structured procedural skill with executable code and a clear step sequence. The main improvement is adding a verification checkpoint and surfacing required imports.

Suggestions

Add a final verification step (e.g., run the TypeScript typecheck or confirm the component appears in PLAYBOOK_COMPONENTS) to close the workflow with a checkpoint.

Show the required imports (PlaybookComponent, JSONSchemaType) so the code template is fully self-contained.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or explanation of concepts Claude already knows; every line (file location, schema, interface, registration) earns its place.	5 / 5
Actionability	Provides concrete file paths and a copy-paste-ready TypeScript template (interface, JSONSchema, component object, registration); minor gaps are the missing imports and placeholder executor body.	4 / 5
Workflow Clarity	Four steps are clearly sequenced (create file, define schema, implement interface, register) with concrete paths; no explicit validation/checkpoint step, though the task is additive rather than destructive or batch.	4 / 5
Progressive Disclosure	Under ~50 lines, single-purpose, and well-organized into Prerequisites and a numbered Procedure with no need for external references.	5 / 5
	Total	18 / 20 Passed

Description

78%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 compact, well-targeted description with an explicit "Use when" trigger and concrete actions tied to a specific interface. It is distinctive and actionable, with only minor room to make the capability statement more explicit.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — "adding a new playbook automation component, implementing a PlaybookComponent interface, or registering a new playbook step" — giving specific, distinct actions rather than vague language.	4 / 5
Completeness	Both "what" (the gerund actions describe the work) and "when" (explicit "Use when:" clause) are present; the "what" is conveyed through the trigger actions rather than a separate capability statement, so it could be more explicit.	4 / 5
Trigger Term Quality	Good keyword coverage with natural developer phrasing ("adding a new playbook automation component", "registering a new playbook step"), though a few synonyms or file-path cues are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (OpenCTI PlaybookComponent interface and playbook steps) with distinct, domain-specific triggers and minimal overlap risk with unrelated skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: OpenCTI-Platform/opencti
Path: .github/skills/create-playbook-component/SKILL.md
Commit: cdafc20

Reviewed: 4 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.