seo-profound

Profound LLM citation tracker (extension). Time-series brand citation rates across ChatGPT, Perplexity, and other LLMs. Pairs with seo-seranking for triangulated AI visibility coverage.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./extensions/profound/skills/seo-profound/SKILL.md

Quality

Content

72%

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 routing/delegation extension, but it lacks executable API call examples and verification checkpoints for its prerequisite workflow.

Suggestions

Add a minimal executable Profound API call example (e.g. an authenticated curl/python snippet returning citation rate) so guidance is copy-paste ready, not just described.

Insert an explicit verification checkpoint in Prerequisites, e.g. 'Before the first call, verify `PROFOUND_API_KEY` is present in `~/.claude/settings.json`; if absent, re-run install.sh.'

Dimension	Reasoning	Score
Conciseness	The body is lean with no conceptual padding (no 'what is an LLM' explainer); every section — prerequisites, routing, output conventions, delegation — earns its place and assumes Claude's competence.	3 / 3
Actionability	It gives concrete routing commands and output conventions, but provides no executable Profound API call code or commands; it describes and delegates rather than giving copy-paste-ready code, matching the level-2 anchor.	2 / 3
Workflow Clarity	Prerequisites are sequenced (install → API key → check settings.json) and the routing table maps commands to purposes, but there are no explicit validation/verification checkpoints (e.g. confirming the API key is set before the first call), which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	It is a short, well-organized skill under 50 lines with no bundle files present, so per the simple-skills scoring note well-organized sections warrant a 3 without external file references.	3 / 3
	Total	10 / 12 Passed

Description

72%

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 is specific, distinct, and uses strong natural trigger terms, but it lacks an explicit 'when to use' clause, which caps completeness and leaves it without clear invocation triggers.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants LLM brand-mention tracking, citation rates across ChatGPT/Perplexity, or week-over-week AI visibility trends.'

Enumerate the concrete actions the skill performs (e.g. 'tracks citation rates, surfaces top prompts, flags competitor co-citations, alerts on spikes') to raise specificity from a capability description to an action list.

Dimension	Reasoning	Score
Specificity	It names the domain and concrete metrics ("Time-series brand citation rates across ChatGPT, Perplexity") but does not enumerate multiple discrete actions in the manner of 'extract/fill/merge'; capabilities are described rather than listed comprehensively, matching the level-2 anchor.	2 / 3
Completeness	The 'what' is clear (citation tracker, time-series rates) but there is no 'Use when...' clause or explicit trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	It uses natural user vocabulary — "LLM citation", "brand citation rates", "ChatGPT", "Perplexity" — that a user would actually say, giving good coverage of relevant terms.	3 / 3
Distinctiveness Conflict Risk	It carves a clear niche (Profound LLM brand-mention tracking) and explicitly pairs with seo-seranking, making it unlikely to trigger for the wrong sibling skill.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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: AgriciDaniel/claude-seo
Path: extensions/profound/skills/seo-profound/SKILL.md
Commit: 09d37c7

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.