---
title: "The installed task skills"
description: "The installer publishes task workflows beside the server configuration."
canonical: index.html
navigation-title: "Task skills"
---

<a id="the-installed-task-skills"></a>

# The installed task skills

The installer publishes task workflows beside the server configuration. A client
chooses one from its description, loads it for the task, and follows the order
it defines. The MCP tools supply the project and TYPO3 facts that order needs.

This is the ordinary set written by `install` and refreshed by `update`. The
path depends on the client and [Installing the server](../installing.md) lists it. The generic
install writes it below `.agents/skills`. Each installed directory also gets
`references/base.md`, the shared start of every workflow. So a copy of the
source directory by hand does not produce the same skill.

The install publishes every skill this server carries, and this lists all of
them. [Checking that it answers](../checking-it-answers.md) explains how to tell a stale copy from a
workflow the client did not activate.

<a id="published-workflows"></a>

## Published workflows

Each name opens one page that contains the unchanged Markdown workflow and every
reference it hands to the agent. The description after it is the skill's own
selection description.

The list stands in the published site only. Read as a file in the repository,
this page ends here, and [skills/](https://github.com/TYPO3/dev-companion/tree/main/skills) is where the same
workflows live.

**[TYPO3 Backend Module Development](typo3-backend-module-development/index.md)**

`typo3-backend-module-development`

Build or change a TYPO3 backend module: registration, controllers,
routes, backend templates, buttons, status markers, labels and icons. A
content element's backend preview in the page module is not a module and
belongs to content-element work.

**[TYPO3 Content Element Development](typo3-content-element-development/index.md)**

`typo3-content-element-development`

Build or refactor TYPO3 content elements and the shared frame they all
render in, replacing that frame included where a package drops the
extension supplying it. Both sides, what an editor fills in and sees in
the page module and what a visitor gets. Use for CType registration,
TCA, child records, backend previews, TypoScript, Fluid, labels and
tests.

**[TYPO3 Core Issue Triage](typo3-core-issue-triage/index.md)**

`typo3-core-issue-triage`

Find the issues worth working on in an area of the forge.typo3.org
backlog — old or untouched ones, and whether anybody is on one already —
or say what is still true about one issue: whether it still happens
against the core checkout, was fixed, or was never a defect. A task that
ends in a patch starts here; the patch is
typo3-core-patch-development's.

**[TYPO3 Core Patch Checkout](typo3-core-patch-checkout/index.md)**

`typo3-core-patch-checkout`

Get a patch under review on review.typo3.org into a core checkout and
out again — onto the branch it targets, into a git worktree beside it,
cherry-picked onto current code, or as the base for extending somebody
else's change. Trying one out, seeing whether it still applies, leaving
the checkout clean. Pushing is typo3-core-patch-development.

**[TYPO3 Core Patch Development](typo3-core-patch-development/index.md)**

`typo3-core-patch-development`

Write a TYPO3 core patch and carry it to review: the changelog entry,
the project's checks, the push to Gerrit. Also amending after review and
backporting to a release branch.

**[TYPO3 Core Patch Review](typo3-core-patch-review/index.md)**

`typo3-core-patch-review`

Review a TYPO3 core patch — your own before you push it, or somebody
else's patch set — and say what is wrong, missing or not ready, in
priority order: the diff, its tests, the changelog entry, the commit
message, the issue reference and the target branch.

**[TYPO3 Development Installation](typo3-development-installation/index.md)**

`typo3-development-installation`

Bring the local development installation of a TYPO3 extension,
sitepackage or project package into existence, or boot and repair the
one the repository declares: the container, DDEV where it declares one,
the unattended install, seeded demo content, and a site that will not
come up.

**[TYPO3 Distribution Content](typo3-distribution-content/index.md)**

`typo3-distribution-content`

Ship the content of a TYPO3 site inside an extension, as a distribution
— the initial content a package carries, the export artifact and the
files beside it, and the site configuration that travels with them. Use
for initial content, data.xml, Initialisation, seeding a page tree, and
a distribution that has to come up on a fresh installation.

**[TYPO3 Extension Asset Build](typo3-extension-asset-build/index.md)**

`typo3-extension-asset-build`

The asset build of a TYPO3 extension, sitepackage or project package:
npm and package.json dependency updates, Dependabot pull requests,
webpack, vite, Grunt or Sass, the built CSS and JavaScript under
Resources/Public, the import map it reaches the backend by, and the core
classes and icons it borrows. Stops at a bundler or library migration.

**[TYPO3 Extension Documentation](typo3-extension-documentation/index.md)**

`typo3-extension-documentation`

Create, update or review documentation for a TYPO3 project or extension:
Documentation/ manuals, README, configuration and integration guides,
examples, migration notes, screenshots and user-facing XLF labels.

**[TYPO3 Extension Health](typo3-extension-health/index.md)**

`typo3-extension-health`

Review a TYPO3 project, sitepackage or extension against its checkout
and active installation and put it right — "look over my repository and
fix it": TCA, services, backend modules, content elements, site sets,
TypoScript, Fluid, labels, icons, security boundaries and deprecated
APIs. The audit reports first; nothing is changed before the list is
agreed.

**[TYPO3 Extension Patch Review](typo3-extension-patch-review/index.md)**

`typo3-extension-patch-review`

Judge one incoming change against a TYPO3 extension, sitepackage or
project package — a GitHub pull request, a patch, a branch somebody
proposes — and say what stops it being merged, from its versions to its
commit message and its checks. It stops at the verdict; the whole
repository is typo3-extension-health's.

**[TYPO3 Extension Testing](typo3-extension-testing/index.md)**

`typo3-extension-testing`

Set up, extend, repair or run tests and static quality checks for a
TYPO3 project or extension: missing test infrastructure, PHPUnit unit
and functional tests, fixtures, Playwright browser and accessibility
tests, PHPStan, php-cs-fixer, baselines and a failing check.

**[TYPO3 Extension Upgrade](typo3-extension-upgrade/index.md)**

`typo3-extension-upgrade`

Keep a TYPO3 extension, sitepackage or project package working on the
TYPO3 and PHP versions it declares, or carry it to another set: code
broken by what a supported major deprecated or removed, adding a new
major, dropping one, and proving every version it claims.