Competitor scan
Compare named competitors on what matters to a decision (price, audience, features, recent moves) from their own public pages.
In Lobstack: Skills › Library › Add
What your agent will do.
Someone needs to know how a product stacks up against named competitors, or who the competitors are.
- 01
Confirm the list and the decision behind it: pricing, a pitch, a roadmap call. With no list, propose five and wait for a yes.
- 02
For each, read their own pricing page, product pages, changelog and docs. Record the date you read each; pricing changes.
- 03
Build one table: company, who it is for, entry price and what it includes, three strongest features, one thing it does not do, most notable move in the last six months.
- 04
Mark anything inferred rather than read. "Price on request" stays that; never estimate a price and present it as found.
- 05
Under the table, What this means: three to five points tied to the decision, including where we are behind. A scan that finds only strengths is not believed.
- 06
Where prices are comparable, add a bar chart of entry and mid tiers in a chart fence.
- 07
Post it as a document with every row linked to its source, and offer to repeat it on a schedule.
Public information only: no trial sign-ups, forms or contacting sales without asking first.
The whole SKILL.md: 35 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: competitor-scandescription: "Compare named competitors on what matters to a decision (price, audience, features, recent moves) from their own public pages."metadata: title: "Competitor scan" category: research tags: [competitors, market]--- ## When to use this Someone needs to know how a product stacks up against named competitors, or whothe competitors are. ## How 1. Confirm the list and the decision behind it: pricing, a pitch, a roadmap call. With no list, propose five and wait for a yes.2. For each, read their own pricing page, product pages, changelog and docs. Record the date you read each; pricing changes.3. Build one table: company, who it is for, entry price and what it includes, three strongest features, one thing it does not do, most notable move in the last six months.4. Mark anything inferred rather than read. "Price on request" stays that; never estimate a price and present it as found.5. Under the table, What this means: three to five points tied to the decision, including where we are behind. A scan that finds only strengths is not believed.6. Where prices are comparable, add a bar chart of entry and mid tiers in a chart fence.7. Post it as a document with every row linked to its source, and offer to repeat it on a schedule. Public information only: no trial sign-ups, forms or contacting sales withoutasking first.
- ResearchFeatured
Research brief
Answer a research question with a sourced brief: the answer first, then the evidence, how confident it is, and what could not be found.
SKILL.md · App - Research
Stress-test a plan
Question a plan or design one point at a time, biggest risk first, until every open point is decided or deliberately parked, then hand back the decisions.
SKILL.md · App - Research
Fact-check a draft
Fact-check a draft: pull out every checkable claim, check each against the source closest to it, and mark it confirmed, wrong (with the fix) or unverified.
SKILL.md · App - Research
Page change report
Check named web pages against the last visit and report only real changes (price, wording, availability, broken parts), quoting before and after.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App