CtrlK
BlogDocsLog inGet started
Tessl Logo

using-oac

Use when starting any conversation — establishes how to find and use OAC skills, requiring Skill tool invocation BEFORE ANY response including clarifying questions, this is your secret weapon to best perform your tasks

56

Quality

63%

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 ./plugins/claude-code/skills/using-oac/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable instruction skill: a clear decision flow, skill inventory, and priority rules make it easy to follow. Its main weakness is repetition across the EXTREMELY-IMPORTANT block and Red Flags table that inflates the token budget.

Suggestions

Collapse the EXTREMELY-IMPORTANT block and Red Flags table into a single concise section to remove restated 'you MUST' messaging.

Trim the 12-row Red Flags table to the few highest-value rationalization traps to reduce token cost.

DimensionReasoningScore

Conciseness

Directive prose is mostly efficient, but the EXTREMELY-IMPORTANT block, the 12-row Red Flags table, and repeated 'you MUST' messaging restate the same rule several ways, adding padding that could be tightened.

2 / 3

Actionability

For an instruction-only skill the guidance is concrete: an explicit invoke-before-respond rule, a decision-flow digraph, a skill table with when-to-invoke, priority order, and friendly-name mapping give clear actionable direction.

3 / 3

Workflow Clarity

A clear multi-step sequence is given via the flowchart (message -> check skills -> invoke -> announce -> todos -> follow -> respond) plus explicit skill priority and type guidance; no destructive/batch operations require validation feedback loops.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is self-contained with well-organized sections (Rule, Available Skills, Priority, Red Flags, Types, Friendly Names) and no nested references, satisfying the well-organized-sections bar.

3 / 3

Total

11

/

12

Passed

Description

42%

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 has a recognizable trigger ('Use when starting any conversation') but the capability statement is vague and padded, and the trigger is so broad it conflicts with all other skills. It communicates intent without the specificity or distinctiveness needed for a strong skill description.

Suggestions

Replace 'this is your secret weapon to best perform your tasks' with concrete capabilities, e.g. 'Determines which OAC skills apply to a task and invokes them before responding.'

Tighten the trigger to a more specific condition rather than 'starting any conversation' to reduce conflict with task-specific skills.

State distinctively what makes this skill unique (meta-skill routing) versus overlapping every task skill's activation.

DimensionReasoningScore

Specificity

Names a domain (finding/using OAC skills) and one concrete action ('Skill tool invocation') but does not list multiple specific concrete actions; 'this is your secret weapon to best perform your tasks' is vague filler.

2 / 3

Completeness

It gives a 'when' (starting any conversation) and a partial 'what' (find and use OAC skills via the Skill tool), but the 'what' is thin and the trigger guidance is weak, so it does not reach the clearly-both-explicit bar.

2 / 3

Trigger Term Quality

'Use when starting any conversation' is a natural phrase but is overly broad and lacks task-specific keywords a user would actually say, missing common variations.

2 / 3

Distinctiveness Conflict Risk

'Use when starting any conversation' is maximally generic; as an always-on meta-skill it structurally overlaps with every task skill, matching the 'very generic; would conflict with many skills' anchor.

1 / 3

Total

7

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
darrenhinde/OpenAgentsControl
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.