Mirror the What/Why/How/Where overview sections from `home.mdx` so
GitHub visitors see the same pitch as the docs landing page.
Also add a static Discord badge at the top, reframe the Discord bullet
in "Getting Started" around the builder focus described in the Discord
announcement post, and rename "About" to "Open development" with a
pointer to `CONTRIBUTING.md`.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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 content of this page is now adequately represented elsewhere:
- The intro, directory structure, and progressive disclosure sections
are covered by `home.mdx` and `specification.mdx`.
- The `SKILL.md` format details are covered by `quickstart.mdx` and
`specification.mdx`.
- The "key advantages" framing (self-documenting, extensible, portable)
is either self-evident, conveyed by the directory trees in `home.mdx`
and `specification.mdx`, or demonstrated by the Client Showcase.
Also adds a redirect from `/what-are-skills` to the home page so
existing inbound links don't break.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Two links in `best-practices.mdx` and `optimizing-descriptions.mdx`
pointed at `/what-are-skills#how-skills-work`, blocking the eventual
removal of `what-are-skills.mdx`. Redirect them to the existing
`## Progressive disclosure` section in `specification.mdx`, which is a
more natural reference target for the concept.
Also expand that section's lead-in from "Skills should be structured for
efficient use of context:" to a sentence that names progressive
disclosure as a loading mechanism, so readers who follow the link land
on a definition rather than a bare set of structural guidelines. The
original three-level list and `SKILL.md` line-count guidance are
preserved unchanged.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The quickstart's "How it works" section already explains progressive
disclosure in concrete, tutorial-specific terms, so the follow-up link
to `what-are-skills.mdx` adds little. Drop it in preparation for phasing
out that page.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Pare the `CardGroup` from five cards across three columns down to two
cards across two columns, keeping only Quickstart (pointing at
`/skill-creation/quickstart`) and Specification. The "What are skills?"
card is now redundant with the "What are Agent Skills?", "Why Agent
Skills?", and "How do Agent Skills work?" sections above, and the "Add
skills support", "Example skills", and "Reference library" links serve
smaller audiences that can reach them through the sidebar.
Also rename the section heading to "Get started with Agent Skills" to
match the neighboring sections, and reword the Specification blurb to
reference Agent Skills rather than `SKILL.md` files.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Collapse the two-row `LogoCarousel` into a single row and compute its
scroll duration from the total cycle width using a fixed
`PX_PER_SECOND`, so scroll speed stays consistent regardless of how many
logos appear or how they are scaled. Drop the now-unneeded vertical
padding on `.logo-carousel-track`.
Rename the "Adoption" heading to "Where can I use Agent Skills?" and
rewrite its blurb to point readers at the Client Showcase page, matching
the question-led style of the neighboring sections.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Adapted from the "How skills work" section of `what-are-skills.mdx`,
with the heading reworded as a question to match the sibling sections,
and the closing sentence rewritten to emphasize the payoff of
progressive disclosure.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Pulls the lightweight-open-format intro, the `SKILL.md` folder
description, and the directory tree from `what-are-skills.mdx` onto the
landing page. Also retitles the page to "Agent Skills Overview" (with
`sidebarTitle: "Overview"`) and refreshes the frontmatter description.
This works toward letting `home.mdx` stand on its own so that
`what-are-skills.mdx` can be phased out in the future.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The "Why Agent Skills?" audience bullets and the "What can Agent Skills
enable?" capability bullets were two angles on the same material, with
direct duplicates between them (e.g. "For skill authors" vs.
"Interoperability", "For compatible agents" vs. "New capabilities").
Collapse both into a single "Why Agent Skills?" section: keep the
problem statement, fold "portable, version-controlled" into the opener,
drop the circular "new capabilities" bullet (absorbing its examples into
"Domain expertise"), and rename "Interoperability" to "Cross-product
reuse". The new "This gives agents:" transition leads into three
non-overlapping bullets.
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>
