\n {skill.name} — examples\n

\n ,\n );\n});\n\napp.get(\"/skills/:slug/files/*\", async (c) => {\n const skill = findSkill(c.req.param(\"slug\"));\n if (!skill) return c.notFound();\n const path = c.req.path.replace(`/skills/${skill.slug}/files/`, \"\");\n if (!skill.files.includes(path)) return c.notFound();\n const content = await readSkillFile(skill.slug, path);\n if (content === null) return c.notFound();\n const isMarkdown = path.endsWith(\".md\");\n const rendered = isMarkdown\n ? await marked.parse(parseFrontmatter(content).body)\n : `

${esc(content)}

`;\n return c.html(\n \n \n ,\n );\n});\n\nexport default app.fetch;\n",[],[236],"aec15f98-c150-4ee9-bee2-4412a486a67e","README.md","bf2513ca-6454-11f1-9006-1607ee4eb77e",["D",1781045797493],"# Skill Library (template)\n\nA forkable directory of reusable **agent skills**. Each skill is a folder of\nMarkdown and code; the app renders every skill's `SKILL.md` and gives you a\none-click **Copy skill** button that puts a ready-to-run payload on your\nclipboard.\n\n🔗 **Live:** https://templates--576a3bb6645411f181421607ee4eb77e.web.val.run\n\n## Getting started\n\nThe intended way to manage this library is with an agent — let it add, edit, and\ndeploy skills for you. You don't need to touch the file tree by hand.\n\n1. **Remix this val** to get your own copy.\n2. **Connect your coding agent** with the Val Town plugin, which bundles the\n Val Town MCP server and platform skills. It works with Claude Code, Codex,\n and Cursor:\n\n ```sh\n npx plugins add val-town/plugins\n ```\n\n See the [plugin guide](https://docs.val.town/guides/prompting/plugin/) for\n per-agent install commands.\n3. **Ask it to add a skill.** For example:\n\n > Add a skill called `pr-summarizer` to my skills val that reads a GitHub PR\n > diff and writes a release note. Put the prompt in `SKILL.md` and a fetch\n > script in `scripts/`.\n\n The agent reads the existing skills for the pattern, creates\n `skills//` with the right files, registers it in the `SKILLS` manifest,\n and deploys — all in place.\n\nPrefer not to set up a local agent? Open this val on val.town and talk to\n**Townie** in the sidebar instead. Same workflow, in the browser.\n\nYou can also just edit a skill by hand — every file opens in the Val Town editor,\ne.g. [`skills/hello-world/SKILL.md`](https://www.val.town/x/dcm31/skills/code/skills/hello-world/SKILL.md).\nA skill's body is plain Markdown, so tweaking wording or fixing a typo is a\ntwo-second edit that deploys on save.\n\n## How a skill is structured\n\nA skill is a folder under `skills//` following the standard Agent-Skills\nlayout, so it stays valid and discoverable by agents reading it outside this app:\n\n```\nskills//\n SKILL.md # entry point — what the skill does and the flow to follow\n scripts/ # runnable code the agent writes locally\n knowledge/ # reference docs the agent reads for context\n assets/ # optional HTML fragment, shown as a live example\n```\n\nOnly `SKILL.md` is required. Each skill is also listed in the `SKILLS` array in\n`lib/skills.ts` (`slug`, `name`, `description`, `category`, and its `files`),\nwhich drives the home grid, the sidebar file tree, and the copy payload — your\nagent keeps this in sync for you.\n\n## Live examples\n\nA skill can ship a live preview — a working UI rendered right on its page, so you\ncan see what the skill produces instead of just reading about it.\n\nTo add one, drop an HTML fragment in the skill's `assets/` folder (e.g.\n`assets/showcase.html`) and list it in the manifest's `files`. That's it — the\napp renders the first `assets/*.html` it finds as an **Examples** panel on the\nskill page, and also serves it standalone (and embeddable in an iframe) at\n`/skills//example`.\n\nThe fragment is just HTML; it can pull in CSS or a `\n \n

History · skills