CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oma-security

Scan application source, agent skills, and MCP components; run penetration tests against scoped web test deployments, validate findings, and configure scan gates. Use oma-qa for broad quality reviews and domain skills for remediation.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 tightly written orchestration skill with an unusually strong workflow: sequenced steps, explicit validation gates, a failure/recovery table, and unambiguous exit criteria. The main costs are repetition of authorization rules across sections and a dense inline body that leans heavily on resource files whose presence could not be verified in this bundle.

Suggestions

Consolidate the authorization/spend rules that currently appear in Dependencies, Resource scope, and Guardrails into a single pointer to the shared execution policy to cut redundant tokens.

Move engine-adjacent operational detail (e.g., the ARTEX snapshot pinning rules in Guardrails) into the corresponding resources/artex.md, keeping the body to selection and flow decisions.

Verify the resources/*.md paths resolve in the packaged bundle, since none were present alongside SKILL.md to confirm the references are real files.

DimensionReasoningScore

Conciseness

The body is dense, directive prose that assumes Claude's competence and never explains known concepts, but authorization/spend rules recur across Dependencies, Resource scope, and Guardrails, and several sentences could be consolidated. This fits 'efficient with minor trimming possible' rather than a lean 5 or a padded 3.

4 / 5

Actionability

For an instruction-only orchestration skill the guidance is actionable: concrete artifact paths ('.agents/results/security/<run-id>/run.json'), a YAML outputs contract, enum vocabularies ('validation: unreviewed | supported | refuted | inconclusive'), a target-to-engine table, and a 10-step workflow. It stops short of fully executable because all actual engine commands are deferred to resource files.

4 / 5

Workflow Clarity

The canonical workflow lists ten explicitly sequenced steps with validation checkpoints (independent verification at step 7, contract checks at step 9, 'confirmed requires independent observed proof'), plus a failure/recovery table providing feedback loops and defined exit states. This matches the top anchor; checkpoints are explicit rather than implicit, so it is not a 4.

5 / 5

Progressive Disclosure

The References section is well organized: 13 resources, one level deep, each with an explicit load trigger such as '(CI requested)' or '(skill target selected)'. It falls short of a 5 because the inline body is a long policy wall with some content that could live in the resource files, and the referenced resources/*.md files are not present in the bundle to verify.

4 / 5

Total

17

/

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, well-scoped description with concrete actions and clean differentiation from sibling skills. Its one structural weakness is the absence of explicit 'when to use this skill' trigger guidance, which caps completeness and slightly weakens trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to scan a repository, skill package, or MCP component for vulnerabilities, run a scoped pentest, or triage/validate scanner findings'.

Include natural user vocabulary such as 'vulnerabilities', 'security audit', and the engine names (Deepsec, Cisco Skill/MCP Scanner, ARTEX) that the body's intent signature already lists as explicit triggers.

Keep the oma-qa routing sentence but pair it with the positive trigger clause so 'when to use' is stated, not just implied by contrast.

DimensionReasoningScore

Specificity

The description lists four concrete actions with scoped targets: 'Scan application source, agent skills, and MCP components', 'run penetration tests against scoped web test deployments', 'validate findings', and 'configure scan gates'. This is comprehensive coverage of the skill's capabilities, matching the 5 anchor rather than 4, whose 'minor gaps' would require a missing core capability.

5 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause for this skill; the second sentence ('Use oma-qa for broad quality reviews and domain skills for remediation') routes to other skills rather than stating when to use this one. Per the rubric guideline, missing explicit trigger guidance caps completeness at 3, with 'when' only weakly implied by the scanning vocabulary.

3 / 5

Trigger Term Quality

Natural phrases like 'penetration tests', 'scan', and 'MCP components' are present, but common user phrasings such as 'vulnerabilities' or 'security audit' and the engine names users would actually say (Deepsec, Cisco, ARTEX, Cloudflare) are missing. Good coverage with a few natural terms absent fits 4, not the comprehensive synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear security-scanning niche (source/skill/MCP scanning, scoped pentests, finding validation, scan gates) and explicitly disambiguates the nearest sibling ('Use oma-qa for broad quality reviews'). Minimal conflict risk fits the 5 anchor; it is not a 4 because the closest overlapping skill is explicitly routed away.

5 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

first-fluke/oh-my-agent

Path

.agents/skills/oma-security/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.