aiox-devops

GitHub Repository Manager & DevOps Specialist (Gage). Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized to push to remote repository. Triggers: git push, create PR, pull request, release, CI/CD, devops, @devops, pre-push, deploy. Use when the u...

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

68%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.

A competently structured activator skill with executable registration steps and clear sectioning, but its destructive remote operations lack inline validation/verification checkpoints and the real command definitions live entirely in external files not bundled with the skill.

Suggestions

Add an explicit validation/verification checkpoint to the remote-git workflow — e.g., after '*pre-push' require quality gates to pass before '*push', and verify the push/PR succeeded before reporting done — so workflow_clarity can exceed the destructive-operation cap of 3.

Inline at least a minimal definition of what '*push' and '*create-pr' execute (or the quality-gate commands '*pre-push' runs) instead of deferring all command detail to the external .aiox-core source-of-truth file.

Resolve the redundant source-of-truth paths (primary .grok/ vs .aiox-core/ vs fallback .codex/) into a single clearly preferred location, and either bundle the referenced files under ./references/ or note explicitly that they live in the host repo.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assuming of competence (numbered protocol, concrete paths, terse starter-command list), with minor trimmable fluff such as the persona/greeting ceremony and the multi-file identity-registration bash block.	4 / 5
Actionability	Provides copy-paste-ready bash for agent registration and prefixed remote commands ('AIOX_ACTIVE_AGENT=devops git push'), but the core devops operations themselves are deferred to external source-of-truth files rather than defined inline.	4 / 5
Workflow Clarity	A clear 7-step protocol with a remote-op precondition exists, but for destructive remote operations (push, PR merge) the validation/quality-gate steps are only referenced implicitly via '*pre-push'/'quality gates pass' and never detailed inline, capping this dimension at 3.	3 / 5
Progressive Disclosure	Well-organized sections with clearly signaled one-level-deep references to a source-of-truth file and a fallback; however the referenced paths (.aiox-core/, .grok/) are external to the skill bundle (no references/scripts/assets present) and cannot be verified, with some redundancy across alternative source paths.	4 / 5
	Total	15 / 20 Passed

Description

95%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.

A strong, specific description with comprehensive natural trigger terms and an explicit exclusivity claim that sharply scopes its niche. The only blemish is a truncated final clause ('Use when the u...') that should be completed or removed.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'repository operations, version management, CI/CD, quality gates, and GitHub push operations' plus 'git push, create PR, pull request, release' — with only minor gaps in coverage (e.g., 'quality gates' is not unpacked).	4 / 5
Completeness	Explicitly answers both 'what' (GitHub Repository Manager & DevOps Specialist with listed operations) and 'when' ('Use for ...', 'Triggers: ...') with concrete trigger phrases; the trailing truncated 'Use when the u...' is a cosmetic defect but does not undermine the explicit trigger guidance already present.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage via 'Triggers: git push, create PR, pull request, release, CI/CD, devops, @devops, pre-push, deploy' — these are exactly the phrases a user would say, including synonyms and the @-invocation form.	5 / 5
Distinctiveness Conflict Risk	Clear niche reinforced by 'ONLY agent authorized to push to remote repository' and specific repo/DevOps triggers, giving minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: SynkraAI/aiox-core
Path: .grok/skills/aiox-devops/SKILL.md
Commit: 4ef6530

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.