growth
Skill8 starsChanged 10 days agoMITView on GitHub
The weekly growth routine for AutoMode: take a metrics snapshot, check every submission in marketing/registry.json, find new lists and directories, and draft the week's posts in one PR. Use it when asked to promote AutoMode, draft social posts, submit to awesome lists or mod catalogues, or report stars and traffic.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- simota/agent-skillstheir own version, first seen Oct 23, 2026
- harshsinghmp/muse-skillstheir own version, first seen Oct 15, 2026
- Weriton-DataOps/Michaeltheir own version, first seen Sep 18, 2026
- arsen-ask-lx/Agent_Quality_Kittheir own version, first seen Sep 16, 2026
- madeehahassan/plsbuild-ostheir own version, first seen Jul 26, 2026
- donatassimkus/claude-ai-skillstheir own version, first seen Jul 23, 2026
Used with
Projects with it also use research.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 4 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- simota/agent-skills★ 99same name
- arsen-ask-lx/Agent_Quality_Kit★ 4same name
- Bappoz/My-Claude-Skills★ 1same name
- donatassimkus/claude-ai-skills★ 1same name
- harshsinghmp/muse-skills★ 1same name
- huangqianqian120/skillslibrary★ 1same name
- madeehahassan/plsbuild-os★ 1same name
- vinitjhawar/opencouncil★ 1same name
- ajsai47/aic-agi★ 0same name
- Weriton-DataOps/Michael★ 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.
In this repository3 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- publish-resultsSkill
- ship-changeSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Run this once a week from local Claude Code.
- Distinctive: line 26
Search GitHub and the web for lists, catalogues and directories that mention effortless, jev-router, claude-router, or Claude Code plugins …
- Very specific: line 33
Add each new place to the registry with reach (stars), last activity, merge rate of its last 30 closed PRs, its rules and tier.
- Distinctive: line 37
Read new releases and merged PRs since the last week.
- Very specific: line 40
Use the site videos in site/public/video/ as assets.
- Very specific: line 41
Run node marketing/tools/post.mts until every post passes.
- Very specific: line 57
Add a number that post.mts rejects, or weaken post.mts to pass a post.
- Distinctive: line 58
Ask anyone for stars or votes.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Grow AutoMode
Run this once a week from local Claude Code. GitHub keeps traffic for 14 days only, so never skip two weeks. Follow ship-change for the PR: one issue and one branch per week, named chore/growth-<yyyy>-w<nn>.
1. Snapshot
node marketing/tools/metrics.mtsReport the stars, unique visitors and top referrers against last week. A new referrer shows which post or list worked. Write it into the result of its registry entry.
2. Check every submission
To check whether a list includes AutoMode, search it for mralexivy, never automode: that word also matches the unrelated mod automodel.
For each entry in marketing/registry.json with open submissions, read the PR or issue with gh. Update its status, and quote any maintainer request in notes. Answer a maintainer question in the next draft, and never with a bump comment.
3. Find new places
Search GitHub and the web for lists, catalogues and directories that mention effortless, jev-router, claude-router, or Claude Code plugins and mods.
gh search code "HeyCubit/effortless" --limit 50 --json repository
gh search repos "awesome claude code" --sort stars --limit 30Add each new place to the registry with reach (stars), last activity, merge rate of its last 30 closed PRs, its rules and tier. Skip a place with no activity in 60 days, a merge rate under 10%, or a topic outside Claude Code and AI coding.
4. Draft
- Read new releases and merged PRs since the last week. Each user-visible change can be one post.
- Draft posts in
marketing/posts/withstatus: draft. Write each one for its channel. Never paste the same text in two places. - Draft each listing entry and PR body by the list's own rules. One line describes what AutoMode does, and the body leads with the benchmark result and its limit.
- Use the site videos in
site/public/video/as assets. - Run
node marketing/tools/post.mtsuntil every post passes.
5. PR
Open the week's PR with the snapshot, the registry changes and the drafts. Its body lists the outward actions the drafts need: which posts to queue, which PRs to open on other repos, which forms to fill in, and the planned dates.
6. After the user merges
- Queue the approved Buffer posts:
node marketing/tools/buffer.mts queue <post> --send. Commit thequeuedstatus on the next week's branch. - Open each approved listing PR on its list from the user's account, one per list. Only do this when the user approves that list in this session.
- Hand the user the Reddit, Hacker News, form and email texts to post themselves.
Never
- Post to Reddit or Hacker News, fill in a web form, or send an email.
- Open a second PR on a list that already has one open.
- Add a number that
post.mtsrejects, or weakenpost.mtsto pass a post. - Ask anyone for stars or votes.
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.

