agentleFS
athina-aiathina-ai/goose-skills/skills/marketing/research-competitors-edge-cases/SKILL.md

research-competitors-edge-cases

Skill1.3k starsChanged 23 days agoMITView on GitHub

Step of the research-competitors playbook: rules for run edge cases such as no browser, stalled workers, earlier reports and late reads. Run research-competitors instead; not for direct use.

1 other project uses a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the athina-ai/goose-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about athina-ai/goose-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

Files
SKILL.md

edge-cases

  • No browser at all (hosted chat, a scheduled run): use the server's free ad sample for tracked rivals (gooseworks:ads_template_read, mode competitor) and whatever fetch can read. Say once, in the report's "In short", what couldn't be read and what it means for the answer; the paid top-up for it is a decision in the closing message, never a question before the report.
  • The browser waits on the founder's approval: tell them in one line what it is for, move on with what you have, and list the page as couldn't-read. Never sit silent.
  • A worker stalls for more than a few minutes: say so in one line. A worker is stopped: keep everything it returned or wrote; never throw read work away.
  • Facts from earlier saved research (dates, figures, launches): re-check them, or mark them "from earlier research, not re-checked".
  • A saved rival that isn't one (a person's account, a namesake, a dead company): drop it, and name it in the report so the founder can fix the list.
  • An earlier report on this brand exists: decide on purpose, and say which in one line — in chat and in the report's first "In short" bullet. Newer than 7 days and the ask doesn't say "fresh" or "update": reuse it as the base — re-check only what moves (news, launches, prices, the conversation) and deliver a what-changed report; never re-deliver it untouched. Older, or the founder asks for a fresh look: refresh in full. A report from today is replaced at the same path. Never treat a saved report's facts as checked without re-checking the ones the new report leads with.
  • A read lands after the report: rewrite the whole report, top lines included. Never patch a section in.
  • Status notes are not questions: one-line notes (the browser heads-up, a stalled worker, a serious risk) are fine before the report; questions are not.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.