CtrlK
BlogDocsLog inGet started
Tessl Logo

competitor-monitoring

Visit each competitor's homepage, features page, pricing page, and blog using Chrome MCP, then write a structured competitive intelligence report saved to Google Drive. Use for a standing weekly competitive pulse or an on-demand deep-dive.

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

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.

A highly actionable, well-sequenced prompt template with strong error-handling checkpoints and clear organization. The only weakness is a short motivational intro that adds tokens without adding instructional value.

Suggestions

Cut or condense the opening motivation paragraph ("Staying on top of competitors manually…") to save tokens without losing instructional value.

Consider tightening the Setup table's Input/Output rows, which partially restate the placeholders section below it.

DimensionReasoningScore

Conciseness

The body is mostly lean and well-structured, but the opening motivation paragraph ("Staying on top of competitors manually means visiting dozens of pages, taking notes, and writing a summary — every week. This skill does all of it…") is unnecessary framing Claude does not need and could be trimmed.

2 / 3

Actionability

Concrete, specific guidance throughout — named pages to visit, exact fields to capture per competitor, a fully specified report structure, a fixed output path, and clear rules ("do not fabricate", "Return the Drive link").

3 / 3

Workflow Clarity

Three clearly sequenced steps with explicit checkpoints for a batch operation: "If no list is found, note it and stop" and "If a competitor's site is unavailable, note it and skip", plus bounded constraints like the 3-sentence executive summary.

3 / 3

Progressive Disclosure

Self-contained skill with no external references needed; content is well-organized into Prompt Template, Setup, Placeholders, and Tips sections that are easy to navigate, satisfying the simple-skill allowance.

3 / 3

Total

11

/

12

Passed

Description

100%

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 description: specific actions, explicit use-when guidance, natural trigger terms, and a distinct niche, all in concise third-person voice. No notable weaknesses.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Visit each competitor's homepage, features page, pricing page, and blog using Chrome MCP, then write a structured competitive intelligence report saved to Google Drive" — naming specific page types and a concrete output artifact.

3 / 3

Completeness

Explicitly answers both what (visit competitor pages and write a structured report to Drive) and when ("Use for a standing weekly competitive pulse or an on-demand deep-dive"), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes natural terms users would say — "competitor", "competitive intelligence", "weekly competitive pulse", "on-demand deep-dive" — giving good coverage of phrasings a user reaches for when needing this skill.

3 / 3

Distinctiveness Conflict Risk

The competitive-intelligence niche with Drive + Chrome MCP and report output is clearly distinct from other skills and unlikely to trigger for the wrong one.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
amplitude/builder-skills
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.