agentleFS
Sign inStart free
ucsandmanucsandman/claude-skills/logo-reveal/SKILL.md

logo-reveal

Skill5 starsChanged 2 months agoMITView on GitHub

Use when the user wants a logo reveal / logo animation / brand intro video for any product (e.g. "/logo-reveal", "make a logo reveal for DashClaw", "animated logo for the landing page").

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read each; verify draw-on progression + transparent alpha (corner pixel alpha 0).

    line 25

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

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

Logo Reveal

REQUIRED BACKGROUND: marketing-studio skill (engine location, brand onboarding); also read C:/Projects/animations/docs/playbook/blender.md and C:/Projects/animations/docs/playbook/remotion.md. Work happens in C:/Projects/animations.

Produces a product-owned logo animation under <product>/marketing/assets/<brand>/. The mark's construction, product verb, material, or environment determines the reveal; a generic glow-and-hold is not the default.

Recipe

  1. Toolchain + brand check per marketing-studio (onboard the brand first if new).
  2. Blender scene: feeders/blender/scenes/logo_reveal_<brand>.py. If missing, copy logo_reveal.py (noban) and swap ONLY the geometry builders to the new mark's SVG shapes — materials/choreography/camera/alpha/args are brand-agnostic. Read C:/Projects/animations/docs/playbook/blender.md FIRST (cleanup, emission 1.0, non-cyclic splines).
  3. Proof frames: python feeders/blender/render.py <scene> --brand <brand> --project <product> --frame 20|55|90, Read each; verify draw-on progression + transparent alpha (corner pixel alpha 0).
  4. Animation render (--animation, ~30s), then node scripts/stage-blender-assets.mjs <brand> --project <product>; product assets and public staging stay in the same product workspace.
  5. Composite: render the LogoReveal composition with product-owned props, output, and --public-dir=<product>/marketing/assets/<brand>/public. Inspect stills at frames 30/80/130 (mid-draw / wordmark in / full lockup, CTA in the brand's accent-positive color).
  6. Deliver the product-owned artifact per marketing-studio.

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