Give your AI coding assistant a set of thin, always-current skills so it knows how to build with Lynkow. Previous: Integration Checklist
The Lynkow AI skills are short instruction files for an AI coding assistant (Claude Code, Cursor, Codex, GitHub Copilot, Windsurf, and others). Each one is a thin router: it tells your assistant the canonical steps for a capability and, above all, where to find exact, current details in the live Lynkow docs. The skills never restate SDK signatures, so they do not go stale. Install the whole set once; your assistant loads only the skill that matches the task at hand.
Where the bundle lives
The bundle ships inside the lynkow npm package. After you install the SDK, it is on disk at node_modules/lynkow/skills/:
npm install lynkownode_modules/lynkow/skills/
├── claude/<name>/SKILL.md # Claude Code format (13 skills)
├── cursor/<name>.mdc # Cursor rules format (13 skills)
└── agents/AGENTS.md # one flat file for AGENTS.md-aware assistantsPick the format your assistant reads and copy it into your project. Three formats, same content.
Install into your assistant
Claude Code
Copy the Claude skills into your project's skills directory:
mkdir -p .claude/skills
cp -r node_modules/lynkow/skills/claude/* .claude/skills/Your assistant now loads the right skill when you ask it to build a Lynkow feature. Start any request with "use the lynkow skill" if you want it to route explicitly.
Cursor
Copy the Cursor rules into your rules directory:
mkdir -p .cursor/rules
cp node_modules/lynkow/skills/cursor/*.mdc .cursor/rules/Each rule is agent-requested: Cursor loads it when your prompt matches its description.
Codex, GitHub Copilot, Windsurf, and other AGENTS.md assistants
Use the single flat file. Append it to your project's AGENTS.md (or copy it as your AGENTS.md if you do not have one yet):
cat node_modules/lynkow/skills/agents/AGENTS.md >> AGENTS.mdWire up docs search (recommended)
The skills tell your assistant to search the Lynkow docs for exact signatures. There are two ways to make that a first-class capability, and you do not need both.
Keyless, no account (default)
The docs expose a public search endpoint your assistant can call directly, and any doc page is available as Markdown by appending .md to its URL. This needs nothing to set up and is what the skills already point at:
Search:
GET https://www.lynkow.com/docs/api/search?q={query}Any page as Markdown: append
.mdto its URL, or sendAccept: text/markdown.
Through the hosted Lynkow MCP (if you already use it)
If you connect your assistant to the hosted Lynkow MCP with an API token, the same capability is exposed as two read-only tools, so your assistant pulls current endpoints and types at generation time instead of guessing:
search_lynkow_docs- full-text search over the Lynkow developer docs.get_lynkow_doc_page- fetch a specific doc page as Markdown.
The endpoint is https://mcp.lynkow.com/mcp, authenticated with a Bearer API token. The same MCP also exposes tools to manage your content, forms, reviews, analytics, SEO, and media; the two docs tools above are the ones that need no site setup.
Claude Code (.mcp.json in your project):
{
"mcpServers": {
"lynkow": {
"type": "http",
"url": "https://mcp.lynkow.com/mcp",
"headers": { "Authorization": "Bearer YOUR_API_TOKEN" }
}
}
}Cursor (.cursor/mcp.json):
{
"mcpServers": {
"lynkow": {
"url": "https://mcp.lynkow.com/mcp",
"headers": { "Authorization": "Bearer YOUR_API_TOKEN" }
}
}
}What the skills cover
One index skill plus one per capability. Install only what you need, or the whole set.
Skill | Builds |
|---|---|
| Start here: routes your assistant to the right skill and sets up the client |
| Blog, articles, categories, tags, pages, global blocks, path resolution |
| Dynamic forms with anti-spam |
| Customer reviews and ratings |
| Instant full-text search of your own content |
| SEO, JSON-LD, sitemap, redirects, tracking, cookie consent |
| Responsive, optimized images |
| Multi-language content |
| Cache revalidation on content change |
| In-page visual editing |
| Product catalog browsing |
| Bookable products, availability, bookings |
| Buyer accounts, login, addresses |
Keeping them current
Each skill points to the live docs rather than embedding details, so the guidance stays fresh on its own. To pick up new skills and refinements, upgrade the SDK and recopy the bundle:
npm install lynkow@latest
cp -r node_modules/lynkow/skills/claude/* .claude/skills/Reference
Complete Integration Checklist - everything you can build, with links to each guide.
Quick Start - create the client and make your first call.
Docs search, used by the MCP and the skills:
GET https://www.lynkow.com/docs/api/search?q={query}. Machine-readable index:/llms.txt. Append.mdto any doc page URL for Markdown.