# Amdahl Skills

> A skills library for go-to-market practitioners (GTM engineers, RevOps and sellers), open to anyone to publish. Each skill has a SKILL.md file: YAML frontmatter (name, description) and markdown instructions. Some skills are a whole folder, the SKILL.md and the files it runs, installed from one tar.gz. Skills are published by Amdahl, an organization or an independent developer. Amdahl's own are written by the Amdahl team; every other skill is checked automatically, not reviewed by Amdahl.

- Page: https://amdahl.ai/skills
- Machine index of Amdahl's own skills (Agent Skills Discovery v0.2.0): https://amdahl.ai/.well-known/agent-skills/index.json
- Every other skill has its own machine index: https://amdahl.ai/skills/<publisher>/<skill>/.well-known/agent-skills/index.json

## Installing a skill

An agent installs a skill by saving its SKILL.md as `<name>/SKILL.md` in a skills folder: `.claude/skills/` in the project for Claude Code (`~/.claude/skills/` for every project), `.agents/skills/` for most other agents. A skill listed with an install file (a tar.gz) is a whole folder instead: it installs by unpacking that file into `<name>/` there.
Each skill below also lists a one-line command that saves it into a Claude Code project by hand.

## Publishers (4)

- [Amdahl](https://amdahl.ai/skills/amdahl) (verified): Official skills from the Amdahl team. Markdown: https://amdahl.ai/skills/amdahl.md
- [SalesEQ](https://amdahl.ai/skills/saleseq) (verified): Call intelligence for sales leaders. SalesEQ turns video calls into coaching evidence, deal risk, follow-up context and revenue visibility. Markdown: https://amdahl.ai/skills/saleseq.md
- [aguvai](https://amdahl.ai/skills/aguvai) (independent developer). Markdown: https://amdahl.ai/skills/aguvai.md
- [canada-site-ops](https://amdahl.ai/skills/canada-site-ops) (independent developer). Markdown: https://amdahl.ai/skills/canada-site-ops.md

## Skills (5)

### Competitor mentions from calls

Finds what prospects and customers say about a competitor or alternative tool on recorded sales and customer calls, including who uses it, what they like and dislike, pricing, and why they switched or stayed. Every claim is checked against the transcript and linked to the moment it was said. Use when someone asks what customers say about a competitor, wants competitive intel or a battlecard based on real calls, wants to know why buyers switch, or asks who mentioned a vendor on calls. Needs call transcripts with speaker names, from a meeting-intelligence MCP server such as SalesEQ or from exported transcripts.

- Name: competitor-mentions-from-calls
- Publisher: SalesEQ (https://amdahl.ai/skills/saleseq)
- Category: Calls
- Published: 2026-10-27
- License: MIT
- SKILL.md: https://amdahl.ai/skills/saleseq/competitor-mentions-from-calls.md
- Install: `npx amdahl skills add saleseq/competitor-mentions-from-calls`
- Needs: Node.js 20 or later, for npx
- Security checks: Format and hidden characters pass (Amdahl file policy, 2026-10-27); Threat analysis pass (Cisco AI Defense skill-scanner, 2026-10-27); Secrets pass (Betterleaks, 2026-10-27)
- Review: Checked automatically, not reviewed by Amdahl.
- Page: https://amdahl.ai/skills/saleseq/competitor-mentions-from-calls

### Discovery question audit

Audits the questions sellers ask across many recorded discovery calls. Sorts each question as open or closed and by depth (basic, deep, business impact), checks coverage against BANT, MEDDIC, SPICED or the team's own framework, and finds the questions that never get asked, the follow-ups that were missed, and the best questions to reuse, each backed by a timestamped quote. Use when a sales leader or rep wants discovery coaching, asks what the team isn't asking, wants a question bank from real calls, or wants to compare reps' discovery. Needs call transcripts with speaker names and timestamps.

- Name: discovery-question-audit
- Publisher: SalesEQ (https://amdahl.ai/skills/saleseq)
- Category: Calls
- Published: 2026-10-27
- License: MIT
- SKILL.md: https://amdahl.ai/skills/saleseq/discovery-question-audit.md
- Install: `npx amdahl skills add saleseq/discovery-question-audit`
- Needs: Node.js 20 or later, for npx
- Security checks: Format and hidden characters pass (Amdahl file policy, 2026-10-27); Threat analysis pass (Cisco AI Defense skill-scanner, 2026-10-27); Secrets pass (Betterleaks, 2026-10-27)
- Review: Checked automatically, not reviewed by Amdahl.
- Page: https://amdahl.ai/skills/saleseq/discovery-question-audit

### Customer ideas to product

Turns what customers and prospects say on recorded calls (feature requests, complaints, workarounds, "is there a way to...", deals blocked by a missing capability) into product opportunities backed by evidence. Separates what was asked for from the problem behind it, groups requests by problem across accounts, checks them against what the product already does, and writes short opportunity briefs with exact quotes and timestamp links. Use when a founder, PM or GTM lead asks what customers are asking for, wants feature requests pulled from calls, needs input for a roadmap, or wants to know which accounts to tell when something ships. Needs call transcripts with speaker names.

- Name: customer-ideas-to-product
- Publisher: SalesEQ (https://amdahl.ai/skills/saleseq)
- Category: Calls
- Published: 2026-10-27
- License: MIT
- SKILL.md: https://amdahl.ai/skills/saleseq/customer-ideas-to-product.md
- Install: `npx amdahl skills add saleseq/customer-ideas-to-product`
- Needs: Node.js 20 or later, for npx
- Security checks: Format and hidden characters pass (Amdahl file policy, 2026-10-27); Threat analysis pass (Cisco AI Defense skill-scanner, 2026-10-27); Secrets pass (Betterleaks, 2026-10-27)
- Review: Checked automatically, not reviewed by Amdahl.
- Page: https://amdahl.ai/skills/saleseq/customer-ideas-to-product

### System diagram

Turn a spec, plan, PRD, Notion page, design doc or a running system into an interactive diagram page: one self-contained HTML file, published as a claude.ai Artifact where that tool exists. The page has a grid of steps (across) by who does each part (down), a side panel that opens every box with a plain sentence first and the technical detail after, and optional pages for a build plan, tables, numbers and open questions. Use when someone says "turn this into a visual diagram", "map this spec", "diagram this Notion page", "make a system map", "visualize this flow", or asks to update, simplify or reflect source changes in a diagram made this way.

- Name: system-diagram
- Publisher: Amdahl (https://amdahl.ai/skills/amdahl)
- Category: GTM engineering
- Published: 2026-10-23
- License: MIT
- Install file: https://amdahl.ai/skills/amdahl/system-diagram.tar.gz (the whole skill folder as a tar.gz, version v0.1.1; unpack it into `.claude/skills/system-diagram`)
- SKILL.md, for reading: https://amdahl.ai/skills/amdahl/system-diagram.md
- Install: `npx amdahl skills add amdahl/system-diagram`
- Needs: Node.js 20 or later, for npx
- Source: https://github.com/amdahlco/system-diagram
- Security checks: not scanned; written and published by the Amdahl team
- Review: Written and published by the Amdahl team.
- Page: https://amdahl.ai/skills/amdahl/system-diagram

### Reposition

Update a marketing site when the company's positioning changes. Reads the positioning input (notes, call summaries, a draft, a brief), drafts the two-line positioning kernel, measures candidate headlines at real size, applies the human's pick, sweeps every page and file that repeats the old story, and records what each decision taught. With Amdahl set up, it pulls buyer quotes from the team's own sales calls. It also checks one headline, tagline or claim against what buyers said on those calls, with no site needed. Use when someone says "we're repositioning", "update the site to the new story", "new tagline", "change the hero", "check this line against our calls", "check our hero against our calls", or when a change touches the site's brand line or outcome line.

- Name: reposition
- Publisher: Amdahl (https://amdahl.ai/skills/amdahl)
- Category: Marketing
- Published: 2026-10-27
- License: MIT
- Install file: https://amdahl.ai/skills/amdahl/reposition.tar.gz (the whole skill folder as a tar.gz, version v0.2.0; unpack it into `.claude/skills/reposition`)
- SKILL.md, for reading: https://amdahl.ai/skills/amdahl/reposition.md
- Install: `npx amdahl skills add amdahl/reposition`
- Needs: Node.js 20 or later, for npx
- Source: https://github.com/amdahlco/landing-site-reposition
- Security checks: not scanned; written and published by the Amdahl team
- Review: Written and published by the Amdahl team.
- Page: https://amdahl.ai/skills/amdahl/reposition

## Submitting a skill

Anyone can publish a skill, free: a person under a name of their own, no organization needed, or a member of an organization listed here. The skill is its SKILL.md: uploaded or pasted (the default), or linked in any public GitHub repository. A person can use the form at https://amdahl.ai/skills/submit. An agent sends JSON to POST https://amdahl.ai/api/skills/submissions, with the SKILL.md text in `markdown` or a GitHub link in `sourceUrl`.

Sending is step one of two. A 6-digit code goes by email to the address sent, and POST https://amdahl.ai/api/skills/submissions/<id>/confirm with `{ "code" }` confirms it; that answer carries a private status link, once. The code proves who the author is: only that address (for an organization, its members) can publish a new version of the skill, check it again or take it down, each with a new code.

Every submitted skill is checked on the spot, then by Cisco AI Defense skill-scanner, Betterleaks and an AI security review. No person at Amdahl reviews it. It is listed on its own when no check fails. A warning from Cisco skill-scanner or Betterleaks shows on its page. What may be a real key waits for its author to remove it or say it is not one. A failed check declines it, with the check, the line and why on the status page and in an email to the author. A check can be wrong: the author can fix the file and check again, or say it is a false alarm. The two scanners' results are public. A warning from the AI review shows on the skill page as what was flagged and the line; its full findings go to the author alone. Amdahl's own skills are published by the Amdahl team, not submitted: a single-file skill is scanned after it is listed; a folder skill (installed from a tar.gz) is not scanned. The full steps for an agent are the skill at https://amdahl.ai/.well-known/agent-skills/amdahl-publish-skill/SKILL.md.

## Reporting a skill

Every skill page has a Report button. Reports also take JSON at POST https://amdahl.ai/api/skills/reports with publisher, name, reason (one of malicious, secrets, impersonation, spam, copyright, other), details (optional; needed for other) and email (required). A 6-digit code goes to that email, and POST https://amdahl.ai/api/skills/reports/<id>/confirm with `{ "code" }` sends the report; a report nobody confirms within 24 hours is dropped. The Amdahl team reads every confirmed report and can take a skill down.

## Publishing as an organization

Any company or open source group can apply to publish under its own name, for free, at https://amdahl.ai/skills/apply. The same form takes JSON at POST https://amdahl.ai/api/skills/org-applications with the fields name, websiteUrl, githubUrl (optional), contactName, contactEmail and description (optional). We email that address a Confirm button and a 6-digit code; the answer's tellUser says what to tell the person, and GET its statusUrl shows when they have confirmed, so an agent never needs their inbox. An application nobody confirms within 24 hours is dropped. Someone at Amdahl reviews each confirmed application by hand, and we email the applicant the decision. Once approved, its members publish under its name: its contact email, confirmed addresses at its own domain when one is set, and the addresses on its member list.

An organization's logo is set by the Amdahl team, or by a member's agent: POST https://amdahl.ai/api/skills/orgs/<organization>/logo with { "email" } emails a 6-digit code; then POST https://amdahl.ai/api/skills/orgs/<organization>/logo/confirm with email, code and the image as multipart `file` (PNG, JPG, WebP, GIF or SVG, up to 2 MB), or JSON { email, code, image } with the image as a data URI. Send remove instead of an image to go back to the monogram. A square mark reads best.

A member's agent edits the organization's name, website, GitHub and description the same way: POST https://amdahl.ai/api/skills/orgs/<organization>/profile with { "email" } emails a 6-digit code; then POST https://amdahl.ai/api/skills/orgs/<organization>/profile/confirm with JSON { email, code } and only the fields to change: name, websiteUrl, githubUrl, description. A field left out stays; an empty githubUrl or description clears it. The address on the page (/skills/<organization>) and who may publish stay as Amdahl set them.

## Also in Amdahl's machine index

Amdahl's machine index also lists the skills for connecting an agent to Amdahl itself (the MCP server, the REST API and agent sign-in). More about Amdahl for agents: https://amdahl.ai/llms.txt
