CtrlK
BlogDocsLog inGet started
Tessl Logo

competitor-analysis

Research competitors and produce a weekly digest of their positioning, launches, and messaging.

58

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./runtime/api-server/src/embedded-capabilities/competitor-watch/skills/competitor-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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.

The content is concise and well-structured for a simple instruction-only skill, but the workflow lacks a validation checkpoint for batch signal collection and the digest-formatting step is not concretely specified. Adding an output template and a verification step would raise the weaker dimensions.

Suggestions

Add a concrete digest template or example so the 'Format a concise digest' step is actionable rather than abstract.

Insert a validation checkpoint, e.g. 'Verify each signal comes from a real public source within the time window before including it.'

Specify where/how to post (which channel, format) to make the final step executable.

DimensionReasoningScore

Conciseness

The body is lean and efficient — a short intro plus four numbered steps with no padding and no explanation of concepts Claude already knows, so every token earns its place.

5 / 5

Actionability

Guidance gives some concrete parameters (sources: site/social/press; 3-5 items; one-line takeaway each) but stops short of executable specificity — 'Format a concise digest' is vague and no output template or example is provided, so it sits at the 'some concrete guidance but incomplete' anchor.

3 / 5

Workflow Clarity

Four steps are clearly sequenced, but the workflow performs batch signal collection with no validation/verification checkpoint (e.g. confirming each signal is real and within the time window), so per the batch-operation cap workflow_clarity cannot exceed 3.

3 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external references; the body is well-organized with a heading, intro, and numbered list, satisfying the simple-skill exception for a top score.

5 / 5

Total

16

/

20

Passed

Description

61%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.

The description clearly states what the skill does using natural domain language, but omits any explicit 'when to use it' trigger guidance, which caps completeness. Specificity is moderate because the lead verb ('Research') is generic despite concrete digest contents.

Suggestions

Add an explicit trigger clause, e.g. 'Use when tracking competitors, monitoring competitive intelligence, or preparing a weekly competitor digest.'

Replace the generic verb 'Research' with more specific actions like 'Collect public signals on... and summarize notable changes.'

Include common synonyms (competitive analysis, market intelligence, rivals) to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

Names the domain ('competitors') and two actions ('Research competitors', 'produce a weekly digest') plus digest contents (positioning, launches, messaging), but 'Research' is generic and coverage is not comprehensive — fitting the '1-2 concrete actions' anchor rather than the 'several specific actions' level above.

3 / 5

Completeness

The 'what' is clear (research competitors, produce a weekly digest of positioning/launches/messaging) but there is no 'Use when...' or equivalent trigger guidance, so per the missing-trigger-clause cap completeness cannot exceed 3.

3 / 5

Trigger Term Quality

Natural terms a user would say ('competitors', 'positioning', 'launches', 'messaging', 'weekly digest') give good coverage, noticeably above the midpoint, though common synonyms ('competitive analysis', 'market intelligence', 'rivals') and an explicit trigger clause are missing.

4 / 5

Distinctiveness Conflict Risk

The competitor-analysis niche is mostly distinct with clear triggers, but there is minor overlap risk with general research or market-analysis skills, placing it just below the minimal-conflict level.

4 / 5

Total

14

/

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
holaboss-ai/holaOS
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.