- 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 add-customer-to-user-list -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add langfuse/langfuse-docs --skill add-customer-to-user-list -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 add-customer-to-user-list -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add langfuse/langfuse-docs --skill add-customer-to-user-list -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/add-customer-to-user-listFrom the publisher
Single source of truth: maintain this skill under
.agents/skills/add-customer-to-user-list/only. Claude and Cursor load projected copies under.claude/skills/add-customer-to-user-listand.cursor/skills/add-customer-to-user-list.
Adds or updates one row in the public adopters table on /users.
Do not write a customer story in this skill. If the user wants a full
/users/<slug> case study, use
customer-story-setup first, then come
back here to link it.
The handbook imports the same table (<AdoptersTable />). Editing the MDX
file updates both pages. Do not duplicate the table elsewhere.
Collect what you can from the request. Ask only for what is still missing:
Then always check for a user story. Do not skip this step.
Search the working tree and origin/main (this branch may be behind):
content/customers/meta.json → pages (skip "index")content/customers/*.mdx — match company name, legal name, or obvious slug
variants (hugging-face vs huggingface, merckgroup vs merck)showInCustomerIndex and quoteCompany if the filename is unclearThe public URL is /users/<slug> where <slug> is the MDX filename without
.mdx.
Never write Langfuse Customer when a user story exists. Prefer the user
story over an external link when both exist.
When the user (or a public source they pointed at) provides a URL and there is no user story:
Link-label examples already in the table:
Blogpost, Tech Blogpost, AWS Blogpost, LinkedIn Post, Job Description,
Case Study, Client Story, Documentation, Release Notes, Research Paper,
Source Code, Conference Talk, Conference Deck, Privacy Policy,
Data Processing Addendum, Subprocessor List, IT White Paper,
Technical Memorandum, Open Source Catalog, OSS LLMOps Stack,
Partner Newsletter
Pick the closest label. Include a date only when it helps (Blogpost from 12/23/2025).
Always include a Wayback Machine archive when the Reference cell is an
external URL. User-story links (/users/<slug>) and Langfuse Customer do
not need one.
Look up an existing 200 snapshot. Always percent-encode the URL with
curl -G --data-urlencode (or equivalent). A raw ?url= query treats &
in the page URL as another CDX parameter and can miss snapshots.
curl -sS -G "https://web.archive.org/cdx/search/cdx" \
--data-urlencode "url=<URL>" \
--data-urlencode "output=json" \
--data-urlencode "filter=statuscode:200" \
--data-urlencode "limit=1"
If CDX is empty, request a snapshot and wait for it. Do not skip this
step or ship the row without an archive. Percent-encode reserved characters
in the page URL (?, &, #) so Save Page Now receives the full URL.
curl -sS -I "https://web.archive.org/save/$(python3 -c 'import urllib.parse,sys; print(urllib.parse.quote(sys.argv[1], safe=":/"))' '<URL>')"
Re-query CDX until it returns a 200 row. The Save Page Now response may
be 5xx even when a capture is stored — trust CDX plus a fetch of the
archive URL.
Confirm the snapshot contains the Langfuse mention (or the cited source content), then use:
https://web.archive.org/web/<timestamp>/<URL>
[Tech Blogpost](https://example.com/post) ([Archive](https://web.archive.org/web/20260304001459/https://example.com/post))
If Wayback cannot capture the page after a retry (common for some LinkedIn
or login-walled URLs), use an archive.ph snapshot the same way neighboring
rows do. Say so in the PR. Do not omit the archive.
Insert alphabetically by company display name (the visible name, not the domain). Update an existing row instead of adding a duplicate.
| [Company](https://www.example.com/) | Short use-case phrase | Langfuse Customer |
| [Company](https://www.example.com/) | Short use-case phrase | [User Story](/users/<slug>) |
| [Company](https://www.example.com/) | Short use-case phrase | [Tech Blogpost](https://example.com/post) ([Archive](https://web.archive.org/web/...)) |
(Wix), (Toyota Group)).# heading
to the table file.Do these only when the company is already on that surface, or the user asks:
Do not add a homepage logo in this skill. That needs a tight wordmark SVG
(no padding; see components/home/img/AGENTS.md) and is a separate request.
content/customers/<slug>.mdx or editing content/customers/meta.json
→ customer-story-setupcontent/customers/ and origin/main for a user storyUser Story, a described external link, or Langfuse Customer[Archive](...) (requested via Save Page Now if none existed)pnpm run format if you edited Prettier-covered files>-
---name: add-customer-to-user-listdescription: >----# .agents/skills/add-customer-to-user-list/SKILL.mdFAQ
Download .agents/skills/add-customer-to-user-list/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.