agentleFS
noamgariani11noamgariani11/claude-skills/skills/user-test-sheevook/SKILL.md

user-test-sheevook

Skill0 starsChanged 3 months agoNo licenceView on GitHub

Sheevook-specialized marketing testing. A senior expert panel - fractional CMO, growth/virality strategist, performance media buyer, brand-positioning strategist, analytics & attribution lead, and community manager - plus a rotating bench of fifteen platform practitioners (X, LinkedIn, Instagram, TikTok, Facebook, YouTube, Reddit, Threads, Bluesky, Discord, Telegram, Pinterest, Snapchat, Tumblr, Hacker News) who each know their own platform's organic algorithm AND its ads manager for real. Tests the core loop (create -> tailor -> approve -> schedule -> publish -> analyze), ad campaign building, the analytics learning loop, the community reply queue, CSV import/export, and journey-stage placement. Scores TWO things: the product UX, and - unique to this skill - the marketing artifacts the app actually generates (would this post perform? would this get removed by a mod? is this ad set structured like a real buyer would build it? is any claim in it fabricated?). Includes domain-accuracy auditing of `lib/tailoring/platforms.ts`, `lib/ads/formats.ts`, and `lib/ads/networks.ts` against `research/` and live platform docs, plus planted-defect calibration that measures what the panel MISSES. Each persona runs as an isolated Agent subprocess. Use when you want "would a real marketing team run their launch on this, and would the content it made actually work?" - not generic UX.

  • Reads credentials

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. About 0 are common, 10 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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.