slim-badges

Badges

Overview

A skill for adding badges to a repository, README, or any document. Badges are small status/label images (rendered via shields.io) that communicate something at a glance — how a document was authored, what standards a project follows, and more.

The skill ships with a small, extensible catalog (see assets/badges.json). The four starter badges are:

Authorship — how a document was written, along the human↔AI spectrum:

Badge	Meaning	When to use
	Written entirely by a human, no AI generation	Hand-written docs, essays, posts you authored yourself
	Human-authored with AI help (drafting, editing, suggestions)	You wrote it but used an AI assistant along the way
	Primarily produced by an AI model	Content generated by an LLM with little human authorship

SLIM — badges for crediting the SLIM project:

Badge	Meaning	When to use
	Project follows SLIM best practices	Projects adopting SLIM guidance

When to Use This Skill

Trigger when the user mentions adding or choosing a badge / shield for a repo or document, wants to disclose authorship (human vs. AI), or asks for the SLIM badge. Keyword cues: badge, shield, slim badge, human made, AI-assisted, AI-generated, best practices.

Workflow

Step 1: Identify which badge(s) the user wants

Read the user's request and scan for keywords, matching against the catalog in assets/badges.json (each entry has a keywords list):

• "human made / human written / no AI" → 100% Human Made
• "AI-assisted / wrote it with AI / copilot" → AI-assisted
• "AI-generated / generated by AI / LLM-written" → AI-generated
• "slim / best practices" → SLIM Best Practices

If exactly one badge clearly matches, proceed. If the request is ambiguous or matches none/several, ask the user which badge they want, presenting the catalog options.

Step 2: Identify the target document

Determine where the badge goes (e.g. README.md, a specific doc, a badges row near the title). If unclear, ask. Check for an existing badges row to append to rather than duplicating.

Step 3: Insert the badge markdown

Each badge is a linked image. Use this pattern (image URL + link URL from the catalog):

[![100% Human Made](https://img.shields.io/badge/%E2%9C%8D%EF%B8%8F%20100%25%20Human%20Made-green)](https://nasa-ammos.github.io/slim/?search=slim-badges)

Ready-to-paste snippets for all four badges:

[![100% Human Made](https://img.shields.io/badge/%E2%9C%8D%EF%B8%8F%20100%25%20Human%20Made-green)](https://nasa-ammos.github.io/slim/?search=slim-badges)
[![AI-assisted](https://img.shields.io/badge/%F0%9F%A7%91%E2%80%8D%F0%9F%92%BB%20AI--assisted-gold)](https://nasa-ammos.github.io/slim/?search=slim-badges)
[![AI-generated](https://img.shields.io/badge/%F0%9F%A4%96%20AI--generated-red)](https://nasa-ammos.github.io/slim/?search=slim-badges)
[![Best Practices from SLIM](https://img.shields.io/badge/Best%20Practices%20from-SLIM-blue)](https://nasa-ammos.github.io/slim/)

Place badges at the top of the document (just under the title) where badges conventionally live.

Offline / self-hosted option: static SVG snapshots of each badge are bundled in assets/ (e.g. assets/human-made.svg). Copy one into the target repo and reference it locally if you prefer not to depend on shields.io at render time.

Badge Catalog Details

id	Label	Color	Link
human-made	✍️ 100% Human Made	green	skill page*
ai-assisted	🧑‍💻 AI-assisted	gold	skill page*
ai-generated	🤖 AI-generated	red	skill page*
slim-best-practices	Best Practices from SLIM	blue	https://nasa-ammos.github.io/slim/

* skill page = https://nasa-ammos.github.io/slim/?search=slim-badges

The authorship badges intentionally use a traffic-light color scheme (green → gold → red) to read at a glance from fully human to fully AI.

Capitalization Rule

When wording a badge label, use title case, but keep the element after a hyphen lowercase unless it is an acronym or proper noun. For example: AI-assisted (AI = acronym → caps; "assisted" → lowercase), AI-generated, 100% Human Made. Follow this rule for any new badge you add.

Extending the Catalog

To add a new badge:

1. Append an entry to assets/badges.json with: id, category, label, color, image_url (a shields.io URL), link_url, snapshot, keywords, and description.
2. Compose the shields.io URL: https://img.shields.io/badge/<LABEL>-<COLOR>.
   • Percent-encode spaces (%20) and emoji (e.g. ✍️ → %E2%9C%8D%EF%B8%8F).
   • Escape literal hyphens inside the label as -- (e.g. AI--assisted).
3. Optionally cache an SVG snapshot: curl -fsSL "<image_url>" -o assets/<snapshot>.
4. Apply the capitalization rule above.

Assets Available

• badges.json — the badge catalog (source of truth).
• human-made.svg, ai-assisted.svg, ai-generated.svg, slim-best-practices.svg — static SVG snapshots of each badge.

Credits

The human/AI authorship-badge concept was inspired by byhumannotai.com.