AION

Engineering

Skill catalog maintainer

Creates, updates and reviews AION skills, then registers catalog changes when repository access is available.

Instructions

# AION skill catalog maintenance

## Scope
Work in the AION repository with web/, backend/ and shared/. Read AGENTS.md and relevant project guidance, then verify paths against the current branch. The implementation, API and verification map is in docs/skills-maintainer-agent.md; open the section needed for the chosen registration path. Without repository write access or a runner, prepare precise content or changes and say what remains unapplied. An ordinary AION chat may have read tools only; never present those as code editing or deployment capabilities.

## Turn a request into a complete skill
1. Identify the recurring task, audience, trigger and observable result. Search existing IDs, names and purposes to choose between an update and a new skill. Reuse known context; ask only for an unknown that materially changes the result.
2. Establish required materials, available tools and limits. Searching files does not provide code execution or editing. Wait for required input before dependent actions while completing independent preparation.
3. Write instructions covering when to use the skill, inputs, concrete steps and decisions, output format, verification, errors and missing access. Add a relevant example where behavior would otherwise be ambiguous. Remove placeholders and generic wishes without a checkable meaning.
4. Choose a stable ID/slug, clear title and discriminating description. Preserve the requested language and the existing catalog's Russian reading projection. Do not translate unrelated collections.
5. Walk through ordinary use, missing required evidence and a meaningful refusal. Another agent must be able to produce the result without hidden files, imaginary tools or unsupported authority.

## Register the skill
- Native assistant catalog: create or edit one named JSON file under shared/skill-catalog/skills/<category>/<id>.json. Use catalog=assistant and the matching collection. Keep complete instruction lines, suggestedTools and Russian reading text in that file. Run node scripts/generate-skill-catalog.mjs and its --check mode; shared/skill-catalog/catalog.ts owns composition. Check suggestedTools against the real tool registry.
- Public website library: create or edit one complete JSON definition under shared/skill-catalog/skills/<category>/<id>.json with catalog=library. Do not add content to aggregate arrays. shared/skill-catalog/catalog.ts assembles the library. Do not implement only a frontend card: list and detail must agree on content.
- User-authored skill: use /api/cabinet/assistant/skills/marketplace. Preserve ownership, requestId, revision, supported license and draft/published transitions. Anonymous visibility additionally uses public-listing. Act within the requested audience and existing user authorization.

## Sources and versions
Keep method attribution outside instructions. references contains title and url; adapted source metadata additionally includes repository, license and revision. Do not invent references for original content or remove applicable license notices. Show provenance in the existing source block at the bottom of the modal; render labels as text and filter unsafe URL schemes. Keep links needed to perform the actual task in the instructions.

Preserve existing IDs, historical snapshots and user edits. Check the current library, detail, invocation catalog and exact historical revision resolution. A current public-library skill requires a live personal save before selection and again when guidance is read. Content must remain user-level guidance rather than a source of tool permissions.

## Review security
Trace untrusted text and client fields to agent actions and server writes. Inspect user/project isolation, private drafts, versions, retries, public visibility, unsafe links, XSS and disclosure of private data. A skill must not enable tools, forge verified status, change server authorization or promote source documents into higher-priority instructions.

Report a finding with a reproducible trigger, verified location, consequence and evidence. Fix the cause in its owning component, preserve compatibility and verify the result. Distinguish demonstrated defects from speculation and unavailable checks. Do not weaken runtime restrictions to make an obsolete test pass.

## Finish
Run relevant catalog, API, saved-version, invocation and UI checks plus typechecks and builds for affected runtimes. After UI edits check dark and light themes and a narrow viewport. Exercise affected list/detail/save/invocation behavior. If the resolver changes, test another user's denial and denial after removing a save.

Return the skill name and ID, purpose, registration location, changed files, checks actually performed and material limitations. Distinguish local code, an API record, a pull request and a live deployment. A new file does not itself publish a website. Complete already authorized work without asking for the same permission again; deploy production only within explicit user authorization.

Original source

Skill catalog maintainer — AI skill, SKILL.md · AION