Abd devops

Skill RealDougEubanks/ClaudeMarketplace/skills/agent-based-development/skills/abd-devops

ABD DevOps agent: scaffolds CI/CD, validates .env.example coverage, checks Dockerfile hygiene, and handles release tasks.From its SKILL.md

Install

npx -y skills add RealDougEubanks/ClaudeMarketplace --skill abd-devops

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

reads credentialsReads from 1 credential source: `.env.example`.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 411 tokens by cl100k_base, as published. Nobody here has run it

ABD — DevOps

Adopt the DevOps role in the Agent-Based Development workflow.

Read the shared references before acting: envelope and artifact rules, Git rules, MVP gate.

If handoffs/ does not exist, stop and tell the user to run the Planning skill (abd-plan) first — see project-start.md.

Instructions:

Use Read to read the latest plan artifact from handoffs/plans/.
Use Glob to check for existing CI/CD config files: .github/workflows/**, bitbucket-pipelines.yml, .gitlab-ci.yml, Dockerfile, and docker-compose.yml.
If no CI/CD configuration exists, use Write to scaffold a GitHub Actions workflow (.github/workflows/ci.yml) with jobs for lint, test, and build.
Validate that all required environment variables documented in the plan have corresponding entries in .env.example; add any that are missing. Never copy real secret values into .env.example or workflow files — placeholder values only (e.g. API_KEY=your-api-key-here).
Check Dockerfile hygiene: verify that a non-root user is set, the base image is pinned to a specific digest or version tag, and a .dockerignore file is present — report or fix each gap found.
For release tasks, follow the release steps in Git rules: open a PR from the release branch into main and tag the release.
Use Write to create a DevOps artifact at handoffs/dev/{taskId}_devops_{unixTimestamp}.json with status and a summary of all checks performed and changes made.

Follow the output format in envelope.md when reporting.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most ship operate skills give in 411 tokens

Counted across 1,077 of the 1,713 authors here whose files we hold, read 2026-09-06

Create GitHub releasein 44 of 1077, across 43 files
Run the test suitein 30 of 1077, across 25 files
Create and push git tagin 27 of 1077, across 26 files
Push commits and tagsin 27 of 1077
Create annotated tagin 25 of 1077, across 22 files
Ensure working tree is cleanin 24 of 1077
Check for product marketing context firstin 23 of 1077, across 6 files
Commit version bump changesin 22 of 1077, across 21 files
Update CHANGELOG.mdin 21 of 1077, across 20 files
Structure launch marketing across three channel typesin 20 of 1077, across 5 files
Commit and tag the releasein 20 of 1077, across 18 files
Update the CHANGELOG for new releasesin 19 of 1077

Said here and by no other author read

Read the shared references before acting
Read the latest plan artifact from handoffs/plans
Scaffold a GitHub Actions workflow if none exists
Validate environment variables in env.example
Check Dockerfile hygiene and fix gaps
Follow the release steps in Git rules

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.