Create Skill

by val-town2d3ec654b6a7No licenseListed Oct 8, 2026Updated Oct 8, 2026

Use when the user wants to persist a preference, skill, or knowledge. Use when it would aid future val development to store a memory of how best to build something.

Instructions onlyAI & Agents
AI-generated overview

Explains how to author Val Town SKILL.md files so AI agents can discover and use user preferences.

What it does
This skill documents the structure and conventions for creating skills in Val Town, where a user places a SKILL.md file under a /skills/ / directory inside a val. It covers required frontmatter fields (name, description, optional triggers), notes that skills without frontmatter are silently skipped, and lists authoring best practices such as being concise and writing in third person. It also describes remixing an existing skill to create a new one.
When to use it
Use it when a user wants to persist a preference, skill, or piece of knowledge for future agent use, or when storing guidance on how best to build something. It fits authoring or customizing a Val Town skill file.
Requirements
No scripts or packages; it is instructions only. It assumes the Val Town environment and its MCP server, and references external Claude Platform documentation.

Skills in Val Town instruct Townie and other AI agents using the Val Town MCP server how to write idiomatic vals that respect a user's preferences and knowledge.

In any val, a user can create a /skills/<name>/SKILL.md file, e.g. /skills/design/SKILL.md. Townie and the Val Town MCP server index skills with that directory/file structure across all of a user's vals. A user may choose to centralize their skills in one val or co-locate skills across multiple vals.

Frontmatter

A skill markdown file must have frontmatter:

  • name: kebab-case name of the skill; contains lowercase letters, numbers, and hyphens
  • description: helps the agent decide when the skill is relevant. A good skill description is critical for agent discovery
  • triggers: (optional) is a list of keywords to tip off the agent

The description and triggers fields enable skill discovery, i.e. tells the user's AI agent (e.g. Claude Code, Codex, Cursor) when to use it. The more specific the better, including key terms that should trigger use (which can also be enumerated in triggers). Skills without frontmatter will be silently skipped, so Townie/MCP will not be able to access them.

Best practices

The Claude Platform Docs offer skill authoring best practices, including:

  • Be concise. The context window is a public good
  • Always write in third person
  • Default assumption: AI agents are already very smart
  • Be as specific as possible (e.g. code is better than plain english where possible)
  • Improve skills based on usage and testing

Example

md
---name: designdescription: Use when styling a val's UI. Use for frontend vals that return JSX or HTMLtriggers: [css, styling, layout, theme]---
- Use `.css` files, avoid inline styles and Tailwind- Locate React components in a `/components` directory, one component per file- Use a sans-serif web-native font stack, no external fonts- ...

Remixing

A new skill can be created by remixing another user’s skill and customizing the SKILL.md file. There is a remix button in the val.town UI, and a remix_val tool in the Val Town MCP server to do so.

Source and attribution

Source:val-town/pluginsinplugin/skills/create-skillat commit2d3ec65

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal