- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add langfuse/langfuse-docs --skill customer-story-setup -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add langfuse/langfuse-docs --skill customer-story-setup -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add langfuse/langfuse-docs --skill customer-story-setup -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add langfuse/langfuse-docs --skill customer-story-setup -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/langfuse/langfuse-docs/tree/HEAD/.agents/skills/customer-story-setupFrom the publisher
Single source of truth: maintain this skill under
.agents/skills/customer-story-setup/only. Claude and Cursor load projected copies under.claude/skills/customer-story-setupand.cursor/skills/customer-story-setup.
Turns a plain Markdown draft into content/customers/<slug>.mdx in the
same pattern as content/customers/canva.mdx and cresta.mdx.
Do not guess. If any item below is missing from the user's draft or message, ask explicitly and wait for answers (or confirm defaults).
authors={["..."]})Produce a numbered checklist for the user (and keep it in the PR description if useful):
public/images/customers/<slug>/<Frame fullWidth> around markdown images, e.g.  per site conventionssips -g pixelWidth -g pixelHeight <file> to get dimensions):
<div className="flex justify-center"><Frame fullWidth className="w-1/2">...</Frame></div><div className="flex justify-center"><Frame fullWidth className="w-2/3">...</Frame></div><Frame fullWidth className="w-full">...</Frame> (no centering wrapper needed)If the draft says "screenshot here" without files, list placeholders in MDX with consistent paths so the user can drop files in later.
Ask whether to add sparse internal links. Default policy: only link major product concepts (match what we used on Cresta):
Do not pepper every noun with links. Use paths from llms-docs.txt /
available-internal-links rule so links resolve.
title, date, description, ogImage,
tag: customer-story, author (display string if needed), customerLogo,
customerLogoDark, optional quote fields, showInCustomerIndex.BlogHeader, CustomerQuote (if quote), ImpactChart (if
impact section), CustomerStoryCTA; use Frame for images (global in MDX).BlogHeader: title, description, customerLogo, authors, date;
optional image for hero.BlogHeader). Body uses
## and ###; do not skip levels.<CustomerQuote quote="..." name="..." role="..." company="..." />
role / company with frontmatter so the byline reads "Name, Role at Company"rolew-1/2 centeredw-2/3 centeredw-full<ImpactChart items={[{ area, impact }, ...]} /> (optional)
then <CustomerStoryCTA />.Reference implementations: content/customers/canva.mdx,
content/customers/cresta.mdx.
content/customers/meta.json
"<slug>" to the pages array (with "index" first).sortCustomerStoriesByMetaOrder in
lib/sortCustomerStoriesByMeta.ts, which reads this list. Place the slug
where the card should appear (e.g. last in the list = bottom-right in a
2-column grid).Authors
data/authors.json (key must match BlogHeader
authors).Assets
public/images/customers/<slug>/.Users / adopters list
add-customer-to-user-list
so the Reference cell is [User Story](/users/<slug>).authors keys exist in data/authors.jsonmeta.json includes slug in desired order-) - the linter will do this anyway; better to do it upfrontAGENTS.md / documentation-pages.mdc: one H1 via BlogHeader, American English, accessible alt text---
title: "..."
date: ...
description: ...
ogImage:
tag: customer-story
author: ...
customerLogo: "/images/customers/<slug>/...-light.png"
customerLogoDark: "/images/customers/<slug>/...-dark.png"
customerQuote: "..."
quoteAuthor: "..."
quoteRole: "..."
quoteCompany: "..."
showInCustomerIndex: true
---
>-
---name: customer-story-setupdescription: >----# .agents/skills/customer-story-setup/SKILL.mdFAQ
Download .agents/skills/customer-story-setup/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/langfuse/langfuse-docs.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.