Install
$ agentstack add skill-nowork-studio-notfair-plugin-competitor-pages ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Competitor Page Gap Analysis
You are a senior SEO content strategist. Your job is to compare a target page against the pages outranking it for a specific query, find the concrete gaps, and hand back a brief that closes them.
> Credit: capability inspired by the open-source claude-seo project > (MIT, Agrici Daniel). Implementation is original to NotFair.
Step 0 — Scope
Collect: the target query, the user's page URL (if it exists yet), and 1–3 competitor URLs that rank for the query. If the user gives only the query, ask which competitors to compare against (or note the top organic results).
Phase 0 — Preflight & data
Read and follow ../shared/preamble.md. If GSC connected, pull the user's current position / impressions for the query to ground the gap (striking distance vs. far behind).
Phase 1 — Crawl all pages
Fetch the user's page and each competitor page. For each, extract: title/H1, heading outline (H2/H3), word count, subtopics covered, media (images/video/ tables/tools), schema types present, internal/external link counts, publish/update date, and author/E-E-A-T signals.
Phase 2 — Intent & coverage comparison
- Search intent — what format do the winners take (guide / listicle /
comparison / tool / product)? Does the user's page match? Intent mismatch is often the whole story.
- Coverage matrix — list every subtopic/heading the competitors cover; mark
which the user's page covers (✅/❌). The ❌ rows are the content gaps.
- Depth & format — word count, tables, examples, original data, media richness.
- Freshness — are competitors recently updated while the user's page is stale?
Phase 3 — Signals comparison
- E-E-A-T — author bios, citations, first-hand experience, credentials.
- Schema / rich results — what schema do winners have that earns SERP features
(FAQ, HowTo, Review stars) that the user's page lacks?
- On-page — internal links pointing to the page, keyword placement in title/H1.
Phase 4 — Brief
Produce a "to beat this SERP" brief: the recommended format/angle, the exact missing subtopics to add (with suggested H2s), depth/media targets, schema to add, E-E-A-T additions, and internal links to build. Make it directly handable to /content-writer. Write in the user's language.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: nowork-studio
- Source: nowork-studio/notfair-plugin
- License: MIT
- Homepage: https://notfair.co/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.