company
Skill0 starsChanged 7 days agoApache-2.0View on GitHub
Method for a business seen from the outside: reach, offer, retain, from public surfaces only. Output is a system diagram and a one-channel plan.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- tandregbg/core-claude-skillstheir own version, first seen Nov 1, 2026
- varunmoka7/resume-hypergraphtheir own version, first seen Oct 2, 2026
- devmesh-in/claude-companytheir own version, first seen Aug 25, 2026
- dilanhendadura/company.mdtheir own version, first seen Aug 23, 2026
- MasatoshiSano/seigi-companytheir own version, first seen Mar 22, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- devmesh-in/claude-company★ 8same name
- tandregbg/core-claude-skills★ 4same name
- dilanhendadura/company.md★ 1same name
- MasatoshiSano/seigi-company★ 1same name
- varunmoka7/resume-hypergraph★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Files
Company method
Goal: how the company moves people from first touch to repeat purchase, from what anyone can see.
Public surfaces only: website, pricing page, public changelog, ads library, public filings, public social. Nothing behind a login, no guessing at private numbers; where you estimate, say so.
Sections:
- TARGET — the company, what it sells, stated scale if public.
- REACH — channels actually used, cadence, paid vs. earned (ads library tells you).
- OFFER — tiers, prices, trial shape, the upgrade moment.
- RETAIN — what keeps people: cadence of releases, community, support posture, refund policy.
- FOUND — the one dependency the whole system rests on.
- PLAN — the user's version: one channel, one price, one weekly artifact. Drawn as a diagram in text.
- LOOP — metric the user will track weekly.
- RULES — public signals only · estimates marked · no private data.
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
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.