agentleFS
Sign inStart free
imMamdouhaboammarimMamdouhaboammar/linkedin-animated-infographics/skills/post/SKILL.md

post

Skill14 starsChanged 3 months agoMITView on GitHub

Route LinkedIn infographic requests to the correct complete or focused workflow using the repository helper, capability gates, creative defaults, and artifact contracts.

18 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 3

    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. Distinctive:

    Start here for a LinkedIn infographic, post, GIF, cheat sheet, workflow visual, stack map, UI story, design direction, hook, mascot …

    line 14
  2. Distinctive:

    Use the route intent:

    line 36
  3. Distinctive:

    When Info-stories is active, the resolved Story House from the merged registry is authoritative.

    line 43
  4. Very specific:

    Keep plugin-local defaults active: creative-attractive-restrained palettes and center-first composition with documented exceptions.

    line 46
  5. Very specific:

    Do not silently bypass post-critic or story-verifier on complete shipping paths.

    line 47

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

LinkedIn Animated Infographics

Purpose

Act as the lightweight routing entrypoint for the plugin. Do not duplicate the complete workflow here. Read helper/GUIDE.md, classify the request, inspect the route, then invoke the correct workflow or focused skill.

Use when

Start here for a LinkedIn infographic, post, GIF, cheat sheet, workflow visual, stack map, UI story, design direction, hook, mascot request, render request, or QA request when the correct specialist path is not already explicit.

Inputs

  • user request and source material
  • optional intent override
  • language/output mode
  • optional visual references, UI mockup flag, brand assets, or mascot requirement

Outputs

Return a resolved route containing workflow, skills, agents, capabilities, asset gates, research gates, and local quality gates. For creation requests, hand control to the new-post parent workflow.

Procedure

  1. Read helper/GUIDE.md.
  2. Resolve the request through the deterministic helper when structured routing is useful:
python3 ${CLAUDE_PLUGIN_ROOT}/tools/route_request.py --request "<request>"
  1. Use the route intent:
    • create-post → new-post
    • qa → qa-post
    • render → render-gif
    • design-study → focused design-study worker/Info-stories references
    • mascot-animation → mascots + svg-mascot-animator
    • info-story → focused linkedin-animated-infographics:info-stories composition path
  2. When Info-stories is active, the resolved Story House from the merged registry is authoritative. Do not silently replace it with legacy House 0; House 0 is only a legacy fallback when there is no resolved story brief.
  3. Apply conditional gates before production: Arabic/RTL, UI fidelity, visual-reference diagnosis, and exact official mascot SVG.
  4. For complete creation, require the creative-director concept stage before story-architect. The concept should provide evidence-safe visual/copy hooks and a useful aha mechanic rather than a generic topic restatement.
  5. Keep plugin-local defaults active: creative-attractive-restrained palettes and center-first composition with documented exceptions.
  6. Do not silently bypass post-critic or story-verifier on complete shipping paths.

HOLD conditions

Return a HOLD when the helper reports a blocking asset or gate, especially a missing exact mascot SVG, unsupported evidence, incompatible Story House/Style choice, or a render/verification blocker. Do not invent a route around a blocking gate.

Related components

  • routing authority: helper/GUIDE.md
  • router registry: helper/router.json
  • capability registry: helper/capabilities.json
  • local quality gates: helper/quality-gates.json
  • artifact contracts: helper/artifacts.json
  • research gates: research/capability-notes/gates.json
  • Info-stories skill: linkedin-animated-infographics:info-stories
  • complete workflow: skills/new-post/SKILL.md
  • focused QA: skills/qa-post/SKILL.md
  • focused render: skills/render-gif/SKILL.md

Research gates

The post router does not reinterpret research rules. It passes through the gate IDs returned by the helper, including prose-specificity, voice-preservation, design-dials, structural-originality, reference-dna, contrast-discipline, evidence-traceability, and bounded-verification where applicable.

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