CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oma-market

Research customer pain points, trends, and competitors through the OMA market engine. Use for market discovery or voice-of-customer analysis.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/oma-market/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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, highly operational orchestration skill: exact CLI commands, explicit gates, exit-code handling, and a genuine validate-fix-recheck loop. Its main defect is that the bundle does not back its own references — nearly every `resources/` file the workflow depends on (intent routing, output laws, frameworks, checklist) is absent from the shipped files.

Suggestions

Ship or fix the `resources/` files: the body depends on `resources/intent-rules.md`, `resources/output-laws.md`, `resources/frameworks/{swot,porters-5f,pestel}.md`, `resources/checklist.md`, `resources/error-playbook.md`, and `resources/execution-protocol.md`, but none exist in the bundle (only `references/_shared/runtime/route-selection.md` is present). Either add them under `references/` and update the paths, or inline the minimal content (e.g., the intent classification table) that the skill cannot run without.

Make the example bash block self-contained: define `$QUERY_PLAN_FILE` (or show how the Step 0.75 query plan is written to a file) and replace the `# … upstream Steps 0 / 0.45 …` placeholder with a one-line pointer to where those steps begin in the upstream contract, so the example is copy-paste runnable.

Trim the duplication between Dependencies and the Canonical command path (resolve/update behavior is described twice) and merge the overlapping 'Intent signature' and 'When to use' bullets to save tokens without losing information.

DimensionReasoningScore

Conciseness

The body is dense and operational throughout — it never explains concepts Claude already knows (no 'what is Reddit/SWOT' padding) and assumes competence. Minor redundancy keeps it from a 5: the Dependencies section re-describes `oma market resolve`/`oma market update` behavior that steps 2 and the failure section already cover, and 'Intent signature' overlaps 'When to use'.

4 / 5

Actionability

The 8-step canonical path gives exact, executable commands with exit-code semantics (`oma market detect-trap "<topic>"`, `oma market resolve --json`, `oma market run <args> --emit=compact`) plus concrete output paths. Not a 5 because the example bash block references an undefined `$QUERY_PLAN_FILE` variable and a `# … upstream Steps …` placeholder, so it is not fully copy-paste ready.

4 / 5

Workflow Clarity

The sequence is explicit with real validation checkpoints and feedback loops: detect-trap preflight (exit 2 → REFUSE, stop), resolve gate (ok:false → stop with reason), and step 8's 'run the self-check … fix and re-check' loop, backed by a dedicated Failure and recovery section. This matches the top anchor; it is above 4 because checkpoints are explicit rather than implicit, and the operation is not destructive so no cap applies.

5 / 5

Progressive Disclosure

The References section is well-signaled with one-level-deep pointers and load hints ('load only the selected framework'), but scored against the actual bundle: of the eight referenced paths, only `references/_shared/runtime/route-selection.md` exists — `resources/intent-rules.md`, `resources/output-laws.md`, `resources/frameworks/*.md`, `resources/checklist.md`, `resources/error-playbook.md`, and `resources/execution-protocol.md` are all missing. Navigation that dangles for 7 of 8 targets is more than the 'minor organization gaps' of the 4 anchor, but the clear signaling keeps it above the muddled structure of 2.

3 / 5

Total

16

/

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 solid third-person description that states concrete capabilities and an explicit 'Use for…' trigger clause with natural keywords. It sits just below the top anchors on all dimensions: the 'when' clause could name concrete trigger scenarios, a few natural synonyms ('market research', 'user complaints') are missing, and 'market discovery' invites mild overlap with sibling research skills.

DimensionReasoningScore

Specificity

'Research customer pain points, trends, and competitors through the OMA market engine' lists several concrete, distinct capabilities (pain-point research, trend analysis, competitor analysis, 'market discovery', 'voice-of-customer analysis'). Not a 5 because coverage has gaps — outputs like SWOT/framework briefs and community sources (Reddit, HN, GitHub) that define the skill are absent; above 3 because it goes beyond 1-2 generic actions.

4 / 5

Completeness

It answers 'what' clearly (research pain points, trends, competitors through the OMA market engine) and 'when' explicitly ('Use for market discovery or voice-of-customer analysis'). Not a 5 because the 'when' clause restates the domain rather than giving concrete trigger scenarios (e.g., 'use when the user asks what users complain about or what is trending in a category'); it clears the 3 cap because an explicit 'Use for…' trigger clause is present.

4 / 5

Trigger Term Quality

'customer pain points', 'trends', 'competitors', 'market discovery', and 'voice-of-customer' are phrases users would naturally say when needing this skill. Not a 5 because common synonyms like 'market research', 'user complaints', 'user feedback', and 'competitor analysis' are missing, leaving a few natural trigger terms uncovered.

4 / 5

Distinctiveness Conflict Risk

The 'OMA market engine' framing plus the pain/trend/competitor/voice-of-customer niche carves out a clear domain with distinct triggers. Not a 5 because 'market discovery' is broad enough to overlap with general research/search skills in the same family (the body itself routes between oma-search and oma-scholar), creating minor conflict risk with closely related skills.

4 / 5

Total

16

/

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

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

first-fluke/oh-my-agent

Path

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