CtrlK
BlogDocsLog inGet started
Tessl Logo

omp-roles

Use this skill whenever you need the allowed_tools / skills preset for a sub-agent role before calling spawn_subagent. Trigger especially when user mentions: "role", "spawn_subagent", "allowed_tools", or any OMP role name (executor, architect, analyst, critic, security-reviewer, code-reviewer, qa-tester, planner, explore, debugger, verifier). Also use when a /ultrawork, /ralph, /autopilot, /ultraqa, or /team workflow step asks for role tool/skill configuration.

76

Quality

95%

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

96%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, highly actionable reference skill: concrete code, exact per-role tool/skill lists, and clear source-of-truth pointers with no wasted tokens. Progressive disclosure is the only dimension short of the top anchor, as the bulk role table is inline rather than split into a reference file.

DimensionReasoningScore

Conciseness

Lean and efficient: terse role definitions with exact tool lists, no padding or explanation of concepts Claude already knows, and a compact usage example; every token earns its place.

5 / 5

Actionability

Fully actionable: copy-paste-ready spawn_subagent() call with parameter guidance, plus exact allowed_tools/skills arrays per role and explicit handling of the null-omit case.

5 / 5

Workflow Clarity

As a simple single-purpose skill the action is unambiguous (look up role config, call spawn_subagent), with a clear canonical source-of-truth pointer and explicit batch-mode guidance; no destructive/batch validation is required here so the simple-skill exception applies.

5 / 5

Progressive Disclosure

Well-organized into Role Definitions and Usage sections with a clearly signaled one-level reference to the canonical source files (constants.py, role_prompts.py); the inline role table is appropriately placed as core reference data, with only minor organization room left.

4 / 5

Total

19

/

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 strong, concrete description that clearly states both capability and trigger conditions with comprehensive natural keywords and minimal conflict risk. Its only mild weakness is that the 'what' is a single configuration action rather than a broad list, keeping specificity just below the top anchor.

DimensionReasoningScore

Specificity

Names a concrete action ('need the allowed_tools / skills preset for a sub-agent role before calling spawn_subagent') plus enumerated role presets, with only minor coverage gaps; it is not a fully comprehensive list of all configuration actions, so it sits below the 5 anchor.

4 / 5

Completeness

Explicitly answers both 'what' (allowed_tools/skills preset for a sub-agent role before spawn_subagent) and 'when' ('Trigger especially when user mentions...', 'Also use when a /ultrawork... workflow step asks for...'), matching the anchor that requires concrete trigger phrases for both.

5 / 5

Trigger Term Quality

Comprehensive natural triggers including 'role', 'spawn_subagent', 'allowed_tools', the full OMP role-name list, and workflow commands (/ultrawork, /ralph, /autopilot, /ultraqa, /team), covering synonyms and command forms users would actually say.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (OMP role tool/skill configuration for spawn_subagent) with highly specific triggers (OMP role names, named workflow commands) that minimize overlap with unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
agentscope-ai/QwenPaw
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.