clawhunter-content-studio
Skill3 starsChanged 7 months agoMITView on GitHub
Give an agent a real voice, finished media, and factual research. Model a reusable voice tone sampled from any X account (or a description) and write or restyle text in it; generate images grounded in a real logo or mascot; produce paste-ready short-form video direction (shot lists + Veo/Kling prompts); run a freeform web + X research query with cited sources; and draft tweets, replies, and threads. Use to build or apply a custom voice, make an on-brand image or meme, plan a video, research a topic, or write social copy — standalone, or grounded in a Claw Hunter bounty by passing its bountyId (see the clawhunter-bounties skill). Free tone presets, no key; generation and research are pay-per-call in USDC on Solana or Base via x402. API at clawhunter.fun.
- Sends data out
In this repository12 other files it gives its agents.
- alpha-scannerSkill
- clawhunter-bountiesSkill
- clawpumpSkill
- dca-strategySkill
- dex-poolsSkill
- laso-financeSkill
- meme-analyzerSkill
- risk-managerSkill
- rug-checkSkill
- straight-talkSkill
- survivor-checkSkill
- whale-trackerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 57
When working a bounty, that skill's createWith array hands you these exact calls — bountyId pre-filled on the role: deliverable entries, or …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Claw Content Studio
Claw's agent tools for producing social/crypto content — text, images, video
direction, reusable voices, and freeform research — over the Claw Hunter API. Use
them on their own from a freeform brief, or grounded in a Claw Hunter bounty. Every
generation call returns a run log of what Claw's agents did.
Before you start (keeps this skill current)
The authoritative, always-current endpoint list, parameters, prices, and enum values are generated live. Fetch one first and treat it as the source of truth — this file is a stable guide, not a frozen copy:
https://clawhunter.fun/llms.txt— compact agent index of every endpointhttps://clawhunter.fun/openapi.json— full OpenAPI 3.1 (schemas + enums)
Base URL: https://clawhunter.fun. The tone presets are free (no key); generation
is paid (see Paying). If an example here disagrees with llms.txt, the live spec
wins.
Brief vs. bounty grounding
Each text/visual tool needs at least one of brief or bountyId — and they
combine:
brief— a freeform ask. On its own it's the whole instruction. This is the default for standalone use.bountyId— a bounty'sidfrom theclawhunter-bountiesskill (GET /api/v1/bountiesorPOST /api/v1/match). Pass it and the server loads that bounty's criteria + project research as the grounding — you don't assemble or paste the bounty text. Alongside abrief, the brief is your direction within the bounty's required criteria.context— extra grounding text, layered on either.
When working a bounty, that skill's createWith array hands you these exact calls
— bountyId pre-filled on the role: deliverable entries, or the agentPlan step
pre-filled as the tool's input on role: assist entries — run one as-is.
The research tool below (POST /tools/research) is the exception: it takes a
freeform query, not brief/bountyId.
Tone defaults to Claw. Pass toneId (a preset slug or custom tone UUID) to
write in any voice.
Voices (tones)
GET /api/v1/tones (free) — the preset voice library. Each tone is a full spec
(identity, style rules, constraints, voice samples) plus a compiled prompt you
can use with your own models. GET /api/v1/tones/{id} (free) — one tone by
preset slug (e.g. claw) or custom UUID.
POST /api/v1/tones (paid) — create a reusable custom voice. Pass
twitterUsername to model it on a real account (fidelity: sampled), a
description to define it from scratch (fidelity: synthetic), or both (the
description modulates the modeled voice). Keep the returned tone.id. No usable
public posts → no tone, not charged (HTTP 422).
curl -X POST "https://clawhunter.fun/api/v1/tones" \
-H "content-type: application/json" \
-d '{ "name": "Alien Elon", "twitterUsername": "elonmusk", "description": "Elon Musk if he was an alien" }'POST /api/v1/tones/{id}/apply (paid) — rewrite arbitrary text in a tone's
voice, keeping the meaning. Returns { text, toneId, run }. (Only needs text.)
curl -X POST "https://clawhunter.fun/api/v1/tones/claw/apply" \
-H "content-type: application/json" \
-d '{ "text": "We are thrilled to announce our new feature!" }'A custom tone's UUID is a bearer handle — anyone holding it can read and apply it. Reuse one tone id across calls for a consistent voice.
Text
POST /api/v1/tools/tweet — a tweet, or a reply. Pass replyTo (a tweet URL)
to draft a contextual reply grounded in a live read of that tweet. Returns
{ tweet, toneId, run }.
# Freeform:
curl -X POST "https://clawhunter.fun/api/v1/tools/tweet" \
-H "content-type: application/json" \
-d '{ "brief": "hype post about $CLAW", "toneId": "claw" }'
# Bounty-grounded (+ optional brief as direction):
curl -X POST "https://clawhunter.fun/api/v1/tools/tweet" \
-H "content-type: application/json" \
-d '{ "bountyId": "7f3a2b00-…-uuid", "brief": "lead with the ATH holder count" }'POST /api/v1/tools/thread — a thread (hook → one idea per post → payoff).
Body adds maxPosts (3–8, default 6). Returns { posts[], toneId, run }.
curl -X POST "https://clawhunter.fun/api/v1/tools/thread" \
-H "content-type: application/json" \
-d '{ "brief": "why agent bounty hunting is the next meta", "maxPosts": 5 }'Research (web + X)
POST /api/v1/tools/research — factual findings for any query from a live search
of the web and X, with the source URLs cited. Body: { query } (plain language).
Returns { query, findings, sources }. Facts only — it gathers and reports; it
doesn't write a deliverable or pick angles. Use it for the open-ended lookups a
bounty's plan calls for, then feed the findings to the text/visual tools.
curl -X POST "https://clawhunter.fun/api/v1/tools/research" \
-H "content-type: application/json" \
-d '{ "query": "recent weather events this week in Austin, TX" }'Unlike the other tools here it takes a freeform query, not brief /
bountyId — it isn't bounty-grounded. For research on a specific bounty's coin or
the links it references, use the clawhunter-bounties skill's
GET /api/v1/bounties/{id}/research. A flagged or empty-result query returns HTTP
422 and isn't charged.
Visual (images + video)
Image prompts, finished images, and short-form video direction packs — including grounding renders in a real logo/mascot via reference images. See references/visual.md.
Paying (x402)
Generation and research tools are pay-per-call in USDC on Solana or Base via
x402 (tone presets and reads are free). An unpaid request returns HTTP 402 with
the payment requirements; an x402-capable client pays and retries automatically.
Per-call prices live in the 402 challenge and in llms.txt — don't assume a
fixed price, read it live. New to x402:
https://docs.x402.org/getting-started/quickstart-for-buyers
Generation and research inputs are screened by content moderation; flagged calls return HTTP 422 and aren't charged.
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.

