CtrlK
BlogDocsLog inGet started
Tessl Logo

aiox-devops

Activate the AIOX GitHub Repository Manager & DevOps Specialist agent (Gage). Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized to push to remote repository. Trigger when user asks to devops, or says 'activate devops', 'switch to devops', '@devops'.

59

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.kimi/skills/aiox-devops/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content front-loads a strong command table but then embeds a monolithic YAML configuration that should be split into referenced files, hurting token efficiency and navigation. Workflows have the right shape but rely on absent external files for executable detail and feedback loops.

Suggestions

Extract the full YAML agent-definition block into a referenced file (e.g. references/agent-definition.yaml) and keep only a concise overview plus a clear 'See <file>' pointer in the body.

Eliminate the duplicate command listing — keep either the Star Commands table or the YAML commands section, not both.

Add an explicit validate→fix→retry feedback loop for the push and release workflows in the body itself (not only in the referenced SOP) so destructive operations have visible checkpoints.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: it inlines a large YAML agent-definition block (persona, Portuguese vocabulary, emoji settings) and duplicates the full command list in both a table and the YAML, much of which Claude does not need.

2 / 5

Actionability

Concrete commands and quality-gate invocations are named, but the actual executable workflows are declared to live in absent dependency files; the body describes and configures rather than providing copy-paste runnable steps.

3 / 5

Workflow Clarity

Sequences for destructive/batch operations (push, force push, release) are present with implicit quality-gate checkpoints, but explicit fail→fix→retry feedback loops are not in the body — they live in the referenced SOP — so the destructive-operation cap applies.

3 / 5

Progressive Disclosure

No bundle files exist and the entire agent YAML definition is inlined in the body; references to dependency files are buried inside YAML comments rather than clearly signaled one-level-deep navigation.

2 / 5

Total

10

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, specific, and complete — it names concrete capabilities, provides explicit natural-language triggers, and clearly distinguishes this agent's niche. It is a strong example of the form.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'repository operations, version management, CI/CD, quality gates, and GitHub push operations' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both 'what' ('Activate the AIOX... agent', the listed operations) and 'when' ('Trigger when user asks to devops...'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases and synonyms with explicit triggers: 'activate devops', 'switch to devops', '@devops', alongside domain keywords, giving comprehensive trigger coverage.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear DevOps niche with distinct triggers and the 'ONLY agent authorized to push to remote repository' claim, minimizing conflict with other skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (698 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
SynkraAI/aiox-core
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.