Discreteds Competition Scout
discreteds-competition-scout is a Claude Code plugin for the Idea phase that scrapes comp sites, analyzes patterns, drafts 25-word entries, and saves results to GitHub.
by discreteds · github.com/discreteds/competition-scout
Automate scouting, analysis, and drafting of ultra-short competition entries with GitHub-backed persistence for recurring comp workflows.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install discreteds-competition-scout@discreteds/competition-scoutBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:discreteds/competition-scout") and the paste-ready config with skillselion.get_install_config("plugin:discreteds/competition-scout").
What it does
discreteds-competition-scout is a Claude Code plugin bundle aimed at solo builders and writers who enter Australian-style “25 words or less” promotions and want agent help end to end. It packages scraping, competitive pattern analysis, constrained creative composition, and persistence so you are not juggling spreadsheets and browser tabs for every new comp. The workflow assumes you care about deduplication, tone alignment with past winners, and repeatable scouting across many sites. It is niche compared to generic research skills: the value is operational speed on a specific comp format, not general market validation. Install it when you already run comps as a growth or side-income habit and want GitHub as the system of record for entries and targets.
Highlights
- Playwright-based scraping pipeline for competition targets and site patterns
- Four-stage skill chain: scrape, analyze, compose, persist (compscoutscrape through compscoutpersist)
- Tone and interpretation matrix tuned to 25-words-or-less style constraints
- Entry deduplication and strategy targeting before submission
- GitHub issues workflow to store entries and scouting state
Why builders use it
Manual comp hunting and ultra-tight copy iteration burns hours and you lose track of which sites, angles, and entries you already tried.
You get a repeatable scout-to-entry pipeline with analyzed patterns and versioned entries on GitHub instead of ad hoc notes.
At a glance
- Type - Plugin in Automation.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is discreteds-competition-scout for?
Writers, marketers, and solo builders who systematically enter 25-word-or-less competitions and want Claude Code to handle scraping, analysis, drafting, and GitHub storage.
When should I use discreteds-competition-scout?
Use it during Idea-phase discovery when you are sourcing new comp targets, refining entry strategy, or producing submission-ready microcopy under strict word limits.
How do I add discreteds-competition-scout to my agent?
Add the discreteds/competition-scout repository as a Claude Code plugin, configure Playwright and GitHub access for persist skills, then invoke the compscout* skills in scrape → analyze → compose → persist order.
Comments
Share how you use discreteds-competition-scout, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.