agentleFS
Sign inStart free
KhucHieuNghiKhucHieuNghi/agents-skills/skills/presentation-brand/SKILL.md

presentation-brand

Skill2 starsChanged 13 days agoMITView on GitHub

Prepare a local, traceable brand profile and logo for a problem presentation, using a supplied company website or a clearly provisional fallback.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this component when problem-presentation needs a consistent identity for an offline deck.

    line 8
  2. Very specific:

    Run node <this-skill>/scripts/brand.mjs --title "<deck title>" --output-dir "<deck directory>/brand" with optional --brand-name, --website, …

    line 14
  3. Distinctive:

    Use palette and logo as design inputs, not as evidence for factual claims.

    line 20
  4. Distinctive:

    Keep the logo local to the customer's output.

    line 21

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

Presentation Brand

Use this component when problem-presentation needs a consistent identity for an offline deck. Ask the customer once for the company or brand name and its official website URL. A supplied logo or brand guide can replace the URL. All fields are optional: when unavailable, create a harmonious provisional identity without another brand question. Never present generated identity as official.

Run node <this-skill>/scripts/brand.mjs --title "<deck title>" --output-dir "<deck directory>/brand" with optional --brand-name, --website, or --logo. The command writes brand.json and a local logo asset. Read the profile before making slides. Reuse it on revisions; use --refresh only when the customer changes the source or asks to regenerate.

Use palette and logo as design inputs, not as evidence for factual claims. Keep the logo local to the customer's output. Read the brand workflow for source handling, confidence, safety limits, and the handoff to slide and diagram skills.

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