agentleFS
Sign inStart free
TidalPaladinTidalPaladin/skills/medcognetics-brand/SKILL.md

medcognetics-brand

Skill1 starsChanged 25 days agoApache-2.0View on GitHub

Style MedCognetics documents and presentations with public brand guidance and authorized assets.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Use brand guidance for the requested output format.

    line 8
  2. Distinctive:

    Use a newer authorized company guide when supplied.

    line 10
  3. Distinctive:

    Keep private source content within its authorized output.

    line 12
  4. Distinctive:

    Use an authorized official logo asset supplied by the user or an approved source.

    line 16
  5. Distinctive:

    If no authorized asset exists, omit the logo and report that limitation.

    line 19
  6. Distinctive:

    Do not typeset a replacement wordmark.

    line 20

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

MedCognetics Brand

Use brand guidance for the requested output format. It separates public website observations from authored layout recommendations. Use a newer authorized company guide when supplied.

Keep private source content within its authorized output. Do not add private paths, text, figures, or metadata to this skill or another public artifact. Resolve audience, destination, or classification only when disclosure depends on it.

Use an authorized official logo asset supplied by the user or an approved source. Preserve its colors, proportions, and clear background. Do not reconstruct, recolor, crop, or stretch it. Public visibility does not grant reuse permission. If no authorized asset exists, omit the logo and report that limitation. Do not typeset a replacement wordmark.

Apply the palette, typography, spacing, and format guidance that fits the artifact. Preserve meaning and evidence. Add classification or legal markings only when the user or an authorized source specifies them.

Render the finished artifact and inspect every page or slide. Check clipping, overlap, fonts, contrast, image quality, logo placement, and numbering. Report unavailable assets, substitutions, or rendering limits.

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