CtrlK
BlogDocsLog inGet started
Tessl Logo

apify-competitor-intelligence

Analyze competitor strategies, content, pricing, ads, and market positioning across Google Maps, Booking.com, Facebook, Instagram, YouTube, and TikTok.

62

Quality

73%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/apify-competitor-intelligence/SKILL.md

The canonical home for this skill is apify-competitor-intelligence in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

64%Scale 1-3

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

The skill provides strong actionable guidance with executable commands and a clear multi-step workflow, but is significantly bloated by the inline Actor lookup table which should be in a reference file. The workflow lacks validation checkpoints between running the actor and summarizing results, which is important for operations that can fail or return unexpected data.

Suggestions

Move the 30+ row Actor lookup table to a separate reference file (e.g., ACTORS.md) and link to it from the main skill, keeping only 3-4 common examples inline.

Add a validation step after Step 4 to verify the actor run completed successfully (e.g., check exit code, verify output file exists and is non-empty) before proceeding to summarize.

Add a retry/feedback loop for failed actor runs - e.g., 'If run fails, check error output, adjust input parameters, and re-run.'

DimensionReasoningScore

Conciseness

The massive Actor lookup table (30+ rows) is verbose and could be condensed or moved to a reference file. The workflow steps are reasonably efficient, but the table dominates the skill and inflates token usage significantly.

2 / 3

Actionability

Provides fully executable bash commands for fetching schemas, running actors in multiple output formats, and clear CLI syntax with placeholders. The error handling section gives specific error messages with concrete fixes.

3 / 3

Workflow Clarity

The 5-step workflow is clearly sequenced with a progress checklist, but there are no validation checkpoints between steps. After running the actor (Step 4), there's no verification that the run succeeded before proceeding to summarize, and no feedback loop for partial failures or retries.

2 / 3

Progressive Disclosure

The Actor lookup table with 30+ entries should be in a separate reference file rather than inline. The skill references external scripts (`run_actor.js`) appropriately, but the main file is bloated with the table that could be split out with a clear link.

2 / 3

Total

9

/

12

Passed

Description

82%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong description that clearly communicates specific capabilities and covers relevant natural trigger terms across named platforms. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill. Adding trigger guidance would elevate this from good to excellent.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about competitor analysis, competitive research, market comparison, or benchmarking across hospitality/travel or social media platforms.'

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'analyze competitor strategies, content, pricing, ads, and market positioning' across named platforms. These are clear, actionable capabilities.

3 / 3

Completeness

Clearly answers 'what does this do' with specific actions and platforms, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when' clause caps completeness at 2.

2 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'competitor', 'pricing', 'ads', 'market positioning', plus specific platform names like 'Google Maps', 'Booking.com', 'Facebook', 'Instagram', 'YouTube', 'TikTok'. These are terms users naturally use when requesting competitive analysis.

3 / 3

Distinctiveness Conflict Risk

The combination of competitor analysis with specific platforms (Google Maps, Booking.com, social media) creates a clear niche. This is unlikely to conflict with generic marketing or social media skills due to the explicit competitive analysis focus and platform specificity.

3 / 3

Total

11

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.