Reduce the `scale` from `1.8` to `1.33` to better match neighboring
logos in the showcase. Also point `instructionsUrl` to the Agent Skills
page on fast-agent.ai, and trim trailing whitespace.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The logo is a 256x256 square icon with no wordmark, so at default scale
it appears much larger than the horizontal wordmark logos used by other
clients. Setting `scale: 0.45` brings it in line visually.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Update descriptions to use better-curated quotes from vendor websites.
Also make display names more specific where the entry refers to a
product rather than the parent company (e.g. "GitHub" → "GitHub
Copilot", "Databricks" → "Databricks Genie Code", "Snowflake" →
"Snowflake Cortex Code").
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Clients are now shuffled by default so that alphabetical ordering
doesn't unfairly prioritize certain clients. A segmented icon toggle
(shuffle / A-Z) in the top-right corner lets users switch between
shuffled and alphabetical order. Each click of the shuffle button
produces a fresh random order.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add a dedicated page listing all clients that support the Agent Skills
format. The `ClientShowcase` component renders the shared `clients` data
as a 2-column grid of cards, sorted alphabetically, with each card
showing the client logo, description, and links to setup instructions
and source code when available.
Add `"clients"` to the navigation in `docs.json`.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Move the hardcoded client data array out of `LogoCarousel.jsx` into a
separate `docs/snippets/clients.jsx` module so it can be reused by other
components. `LogoCarousel` now accepts a `clients` prop, and `home.mdx`
imports and passes the shared data. Also extract a `Logo` sub-component
to reduce duplication of the light/dark `<img>` pair.
Update `CONTRIBUTING.md` to point contributors to `clients.jsx`.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Mintlify adds 36px top and bottom margins to `<img>` elements in the
main content area. This caused unwanted vertical spacing in the logo
carousel rows. Adding `!my-0` to each `<img>` removes those margins.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Use a wrapper `<div>` to control each logo's width instead of styling
the `<img>` elements directly. This also replaces inline styles on the
`<a>` elements with Tailwind utility classes (`no-underline`,
`border-none`) and simplifies the map callbacks.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The logo carousel previously used a per-logo `width` property (e.g.
`"120px"`, `"200px"`) with a fallback default of `"150px"`. This made
logo sizing an absolute, context-specific value tied to the carousel
layout.
Replace `width` with a relative `scale` multiplier (e.g. `0.8`, `1.33`)
that each consuming component can apply to its own base width. This
prepares for sharing the logo data array between `LogoCarousel` and
other components, where the base width might differ. Logos without a
`scale` property default to 1.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Vendor descriptions sourced verbatim from each client's own website or
GitHub repository. The `description` field is placed immediately after
`name` in each entry, grouping identity metadata together.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Replace "space-delimited list" with "space-separated string" in both the
frontmatter table and the `allowed-tools` field section. This better
reflects that the value is a YAML scalar, per the given example.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Mintlify enables click-to-zoom on all `<img>` elements by default. This
caused clicking a carousel logo to both open the vendor link in a new
tab AND zoom the logo to fullscreen in the original tab. Adding `noZoom`
disables the lightbox so only the link navigation fires.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Remove the inner hexagon path with white stroke from `docs/favicon.svg`,
leaving a single solid black hexagon to match the updated logo.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
`shuf` is a GNU coreutil which requires `brew install coreutils` on
macOS. Replace it with `echo $((RANDOM % <sides> + 1))` which works in
bash and zsh on both Linux and macOS.
Also reword "true randomness" to "using a random number generator" to
more clearly distinguish programmatic RNG from LLM non-determinism.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Adds a Discord entry to the Getting Started list in `README.md` and
replaces the standalone "View on GitHub" link in `docs/home.mdx` with a
sentence inviting readers to join on GitHub or Discord.
Also applies minor formatting cleanup in `README.md`: bolds the link
text and switches hyphens to em dashes for consistency.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add a third example showing a Python version requirement alongside `uv`.
This complements the existing examples (product targeting and system
tool requirements) by demonstrating version-pinned runtime requirements
— the kind of non-obvious constraint that the `compatibility` field is
useful for.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Adds a tutorial-style quickstart guide that walks the reader through
creating their first Agent Skill — a `roll-dice` skill that teaches an
agent to roll dice using true system randomness. The guide covers
creating the `SKILL.md` file, verifying discovery via `/skills` in VS
Code, testing with a "Roll a d20" prompt, and a brief explanation of the
discovery/activation/execution lifecycle. Includes both bash and
PowerShell command variants, and a note about model variation in
tool-use reliability.
Also adds the quickstart as the first page under "For skill creators" in
`docs.json` navigation.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add a new "Gotchas sections" subsection to "Patterns for effective
instructions" in the best practices guide. Covers what a gotcha is
(environment-specific facts that defy reasonable assumptions), how to
structure them (problem/correction pairs), and why they belong directly
in `SKILL.md` rather than a separate reference file.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Show `csv-analyzer/` (containing `SKILL.md` and `evals/evals.json`)
alongside `csv-analyzer-workspace/` so readers can see the full layout
at a glance.
Closes#238. Closes#239.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The frontmatter `description` already serves as the page subtitle in
Mintlify, so the "This document defines the Agent Skills format." line
was just restating it.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The directory listing is not exhaustive — skill authors can include
other files and subdirectories beyond those shown. Adding a `...` entry
makes this explicit.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Place the field constraints table immediately after the `Frontmatter`
heading so readers see the reference before the examples. Also remove
"(required)" from the heading, wrap examples in a `<Card>`, and relabel
"With optional fields:" to "Example with optional fields:".
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The fenced code blocks showing `SKILL.md` content were labeled as `yaml`
or plain `markdown`. Changing them to `markdown SKILL.md` adds a
filename hint and more accurately reflects that they contain full
`SKILL.md` snippets (including `---` frontmatter delimiters), not just
raw YAML.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
