The Wagtail project has published its official agent skills, and the design is more interesting than the count. In Agent-friendly documentation for your Wagtail tasks, the open source Django CMS announces five skills: API, for “our new API to automate common tasks”; backend; content modeling, for the page tree and StreamField blocks; frontend; and upgrades. “All the skills focus on the expert knowledge needed to complete tasks, not the way specific tasks should be done, we leave that to you.”
The figure is the project’s own and modest: “On average, we see tasks complete on the order of 30% faster with the skills compared to without,” across models, with a fuller benchmark due at Wagtail Space in November. The installation advice is the part to copy. Instead of five files competing for an agent’s attention, the project recommends “one evergreen Wagtail skill plus the Wagtail CLI”: a short file that “will only trigger if Wagtail is involved” and then decides whether to load the backend or frontend skill, pulling “pre-bundled skills files and live developer docs as needed.” The reason is stated plainly: the team wanted results “without having to manage a plethora of skills or having them pollute context on other work.” And the maintenance plan is unusually honest: “we’ll want to unpublish some of our skills as we see them becoming less relevant with newer generations of models.”
The catalog has the thinnest record of any project this series has covered this month. The Wagtail provider page carries one API page, the Wagtail API v2, the read-only content API that has shipped with Wagtail for years. The “new API to automate common tasks” that the first skill covers has no page. Agent skills is unlit, because the skills live in a GitHub repository the record does not yet point at.
The Kin Score is 12.9, emerging band, with discoverability at 66.1 and contract quality and governance at 0.0. The Agent Readiness score is 0.6, human-only, with only the rate limit signal lit. For an open source framework the number reflects how little it publishes as a hosted service, not how well it supports developers, and the post is evidence of the latter. The catalog’s job is to catch up: a pointer to the skills repository and a page for the new API would move this record more than any of its existing pages. Wagtail has shown how to keep skills from crowding out context. The record has not yet been told the skills exist.