agentleFS
neskuchnyneskuchny/content_factory/.claude/skills/approval-pack/SKILL.md

approval-pack

Skill1 starsChanged 2 days agoMITView on GitHub

Assemble the week's single approval pack for the human: all content units for all platforms in one message or page, with previews, variants and a simple way to reply. Use at stage 6.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Very specific:

    If a Telegram channel is connected (channels), send a short summary and a link to the pack.

    line 27
  2. Distinctive:

    Put the questions that block publishing first.

    line 34
  3. Distinctive:

    No filler: one line of context per unit.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

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

Approval pack

The goal is for the human to spend as little time as possible and still answer on every unit.

Format of weeks/<W>/06-approval.md

# Approval <YYYY-Www> — <client>
Summary: N hub units, M adaptations, budget spent X of Y. Quota: met / not met (why).

## Questions (answer in one line)
1. ...

## W44-R01 · Reels · "<topic>"
Preview: <link to file>   Variants: A (hook "…") · B (hook "…") · C (…)
Adaptations: Shorts, Telegram channel, VK, Pinterest
Facts: ✔ checked   AI: no
decision: pending        # Take A | Take all | Not this | Redo: <comment>
comment:

Delivery

  • If a Telegram channel is connected (channels), send a short summary and a link to the pack. Replies are accepted in the format R01 A, R02 not this: too promotional.
  • Otherwise publish the pack as an artifact page or as a file in Google Drive.
  • Copy the human's replies into the decision/comment fields verbatim.

Rules

  • Show the variants of one topic side by side so they are easy to choose between.
  • Put the questions that block publishing first.
  • No filler: one line of context per unit.

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.