Create tessl tiles with docs, rules, and skills.
Does it follow best practices?
Evaluation — 97%
↑ 1.98xAgent success when using this tile
Validation for skill structure
For creating new tiles that are based on already existing context, such as documentation, other tiles, agent .md and .mdc files, etc.
Study the content: Read the existing context that the user wants to transform into a tile. Plan how to restructure and enhance into agent-efficient tile(s). Determine content type using the decision checklist in SKILL.md: docs, skills, or rules (usually just one). Decide on an absolute output path and use it for all subsequent operations.
Create structure: Use the scaffolding method from SKILL.md (MCP tool or CLI) with your absolute output path.
Copy existing content into tile structure: Copy and rename existing files into the scaffolded directories. Do NOT rewrite content — move files first, then edit in place.
Read the relevant format references: Familiarise yourself with the relevant format(s):
Edit copied files in place: Modify the already-copied files to match the required format. Do NOT rewrite from scratch — make targeted edits for clarity, structure, and agent efficiency. Write new markdown files only where gaps exist.
Validate and interpret lint output:
tessl tile lint /absolute/path/to/tileInterpreting results:
src/lib/foo.ts) are expected in documentation tiles — they reference code in the documented repo, not the tile itself. Safely ignored.Fix errors, re-run lint until errors are resolved. Report remaining warnings to the user with explanation.
my-tile/
├── tile.json
├── docs/ # Documentation (optional)
│ └── index.md
├── rules/ # Rules/steering (optional)
│ └── my-rule.md
└── skills/ # Skills (optional)
└── my-skill/
└── SKILL.md