dep

Handles containerization, CI/CD pipelines, and deployment setup.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is highly actionable with concrete file names, a gated ordered CI/CD workflow, and a copy-paste report template, and it sequences deployment work with explicit validation. It is slightly padded by a restating intro and a generic hallucination disclaimer, and all content lives inline in one file with no reference split.

Suggestions

Tighten the opening two paragraphs to avoid restating the Responsibilities bullets, and replace the generic AI-hallucination disclaimer with deployment-specific limitations.

Move the full Output Format report template and the env-var table into a references file (e.g. references/output-template.md) referenced one level deep, keeping SKILL.md an overview.

Add an explicit validate→fix→retry feedback loop for failed deploys alongside the one-pass verification checklist.

Dimension	Reasoning	Score
Conciseness	Quotes "Dep handles everything between 'code that works locally' and 'code running in production'" and "AI agents may occasionally hallucinate or provide incorrect guidance" — the opening two paragraphs restate the bullet list and the Limitations disclaimer is generic boilerplate rather than skill-specific, matching anchor 2; not score 1 (no concept-tutoring padding) but not score 3 (mild restatement and non-specific disclaimer).	2 / 3
Actionability	Quotes concrete artifacts ("Dockerfile", "docker-compose.yml", ".env.example", ".github/workflows/ci.yml"), an ordered mandatory stage list ("lint → test → build → security-scan → deploy"), and a copy-paste-ready report template with an env-var table — matching anchor 3; per the code_vs_instruction note, instruction-only guidance this specific is not penalized for lacking literal code.	3 / 3
Workflow Clarity	Quotes "Pipeline must include these mandatory stages in order" and "No deploy stage runs if any prior stage fails — this is non-negotiable", plus a deployment verification checklist and rollback procedure — a clear sequenced workflow with an explicit gating/validation rule, matching anchor 3; not score 2 (validation/checklist is present, not merely implied).	3 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and the ~130-line body inlines all responsibilities, the full report template, and env vars in one file with no one-level-deep references, matching anchor 2 ('content that should be separate is inline'); not score 1 (clean section organization) and not score 3 (no well-signaled references, content not split).	2 / 3
	Total	10 / 12 Passed

Description

57%

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 clearly identifies a deployment/DevOps niche with relevant trigger terms, but it only states 'what' and omits any explicit 'Use when...' trigger guidance, which caps completeness and trigger coverage. It is concise and distinct from other skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when setting up Dockerfiles, CI/CD pipelines, or deployment configs for tested code.'

Expand trigger terms to natural phrasings users say — Dockerfile, docker-compose, GitHub Actions, deploy, build config — not just 'containerization' and 'CI/CD'.

Replace the abstract 'Handles...setup' with concrete actions like 'Generates Dockerfiles, CI/CD pipeline configs, and .env templates' to lift specificity.

Dimension	Reasoning	Score
Specificity	Quotes "Handles containerization, CI/CD pipelines, and deployment setup" — names the deployment domain and several areas but lists categories rather than multiple distinct concrete actions, matching anchor 2; not score 1 (not vague) and not score 3 (no enumerated specific actions like 'write Dockerfiles').	2 / 3
Completeness	Quotes "Handles containerization, CI/CD pipelines, and deployment setup" — answers 'what' clearly but has no 'Use when...' / 'when' clause; per guidelines a missing trigger clause caps completeness at 2, matching anchor 2; not score 1 (what is present) and not score 3 (no explicit when).	2 / 3
Trigger Term Quality	Quotes "containerization, CI/CD pipelines, and deployment setup" — relevant DevOps terms but missing common natural variations users say (Dockerfile, docker-compose, GitHub Actions, deploy), matching anchor 2; not score 1 (terms are relevant, not generic jargon) and not score 3 (incomplete coverage).	2 / 3
Distinctiveness Conflict Risk	Quotes "containerization, CI/CD pipelines, and deployment setup" — a clearly bounded DevOps/deployment niche unlikely to trigger for the wrong skill, matching anchor 3; not score 2 (not a broad overlap-prone category like 'works with document files').	3 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 6e69f00

Reviewed: 5 days 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.