agentleFS
Sign inStart free
muthuisheremuthuishere/toolnexus/.claude/skills/marketing/SKILL.md

marketing

Skill6 starsChanged 5 months agoMITView on GitHub

Draft and track the launch posts (LinkedIn, X, Hacker News, Reddit) for a toolnexus release in ~/.marketing/toolnexus/<version>/, built only from shipped facts. Runs as the last step of a release. Trigger: marketing for this release, write the launch posts, LinkedIn/X/HN post for vX, what did we post about toolnexus.

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use writing, research and 4 more.

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.
  • alxyrginSkill

    writing

    Создание контента для личного бренда — статьи, посты, туториалы. Use when user asks to "напиши статью", "создай пост", "подготовь контент", "write article", "create content", or when task requires content creation for blogging, LinkedIn, Medium, or other publishing platforms.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    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

  • GoogleSkill

    prototype

    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 4 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read what was already said: Read ~/.marketing/toolnexus/HISTORY.md and the previous version's folder (ls ~/.marketing/toolnexus/, take the …

    line 24
  2. Very specific:

    Record it: After each post: set the draft's header to POSTED <url>, append date · channel · posted · URL to <version>/README.md, and add a …

    line 48

“Common” is measured: kept by at least 6 in 10 of the 23 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Marketing a toolnexus release

Runs as the final step of the release skill, after every registry is verified from outside. It produces drafts only. The owner posts.

Everything lives outside the repo in ~/.marketing/toolnexus/:

pathholds
HISTORY.mdEvery post ever made (date, channel, hook, file) plus the voice that worked. Read first, every time.
history/Full text of past posts.
<version>/facts.mdTHE source. Every claim with its source (CHANGELOG section, standing page, issue/PR), plus honest NOT-claims and "coming next (not shipped)".
<version>/linkedin.md, x.md, hackernews.md, reddit.mdOne draft per channel, header status: DRAFT / STAGED / POSTED <url>.
<version>/assets/Video, poster, screenshots (the docs-site explainer video lives in site/public/).
<version>/README.mdStatus log: date · channel · drafted/staged/posted · URL.

Steps

  1. Read what was already said. Read ~/.marketing/toolnexus/HISTORY.md and the previous version's folder (ls ~/.marketing/toolnexus/, take the latest version before this one: its facts.md, drafts and README log). Keep the voice, do not reuse a hook already in HISTORY.md, and build on it ("last release X, now Y").
  2. Create ~/.marketing/toolnexus/<version>/ and build facts.md first, from:
    • the ## <version> — <date> section of CHANGELOG.md (the release body is the same text),
    • the current standing/benchmark page (site/src/content/docs/standing-*.md, latest month),
    • merged PRs and issues it cites. Nothing unreleased goes in as shipped; put it under "coming next". Copy each entry's "Not done" gaps into the NOT-claims.
  3. Write the drafts from facts.md only. Honest numbers, losses included ("fastest in some languages, level in some, behind in a couple"). Compare product to product (features, workflow, latency, memory), never company stats. No vendor bashing. No vendor names in claims about the library's API (vendors appear only as benchmark competitors or examples).
  4. Channel shapes:
    • LinkedIn: a hook line, a short what-it-is, 3 arrows of what's new, an honest benchmark line, links (repo, docs, standing page), ≤5 hashtags, the video attached.
    • X: a 3–5 tweet thread, each tweet ≤280 chars.
    • HN: a Show HN: title ≤80 chars, the repo URL, and an author first comment that says what it is NOT (no graph orchestration, no hosted platform, no RAG/vector store — that's citenexus).
    • Reddit: one post per relevant sub, after checking the sub's self-promotion rules.
  5. Never post without the owner's explicit go in this conversation. Posting is outward-facing. toolnexus is a personal (github.com/muthuishere) project: post from the owner's personal accounts only, never the Deemwar page or account, and no draft may mention Deemwar or link deemwar.com. When the owner says go, post through the chrome-agent skill (it stages without --confirm; confirm only after the owner approves the staged post). Never hand-roll a browser.
  6. Record it. After each post: set the draft's header to POSTED <url>, append date · channel · posted · URL to <version>/README.md, and add a row to ~/.marketing/toolnexus/HISTORY.md (date, channel, hook, file) so the next release does not reuse the hook.
  7. Report back: the folder path, which drafts exist, and what is waiting on the owner.

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.

Check your setup, free