aiskillstore/marketplace / skills/abdulsamad94/devops-quality
devops-quality
VerifiedCode quality standards, linting rules, and CI/CD principles.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 849 B |
| skill-report.json | config | 13.4 KB |
skill-report.json
View on GitHub{
"schema_version": "2.0",
"meta": {
"generated_at": "2026-07-18T09:46:18.243Z",
"slug": "abdulsamad94-devops-quality",
"source_url": "https://github.com/AbdulSamad94/Hackhaton-SpecsKitPlus/tree/master/.claude/skills/devops",
"source_ref": "master",
"model": "claude",
"analysis_version": "3.0.0",
"source_type": "community",
"content_hash": "9a6f32ab5d1b4f2ad7ccab9abe40d874ac99afb2d4e4ab926da27c34152674ba",
"tree_hash": "f89320a6d93c0513dd19fb1569b0e5ca644ce73e0c350b70951ab6db84a0b997",
"provenance": {
"model_effective": "claude",
"fallback_chain": [
{
"agent": "codex",
"outcome": "failed",
"error": "2026-07-18T09:46:18.387151Z ERROR codex_models_manager::manager: failed to refresh available models: Missing environment variable: `HELM_API_KEY`.\n2026-07-18T09:46:18.406724Z ERROR codex_models_manage…"
},
{
"agent": "claude",
"outcome": "success"
},
{
"agent": "codex",
"outcome": "failed",
"error": "2026-07-18T09:47:47.318854Z ERROR codex_models_manager::manager: failed to refresh available models: Missing environment variable: `HELM_API_KEY`.\n2026-07-18T09:47:47.339069Z ERROR codex_models_manage…"
},
{
"agent": "claude",
"outcome": "success"
}
],
"analysis_version": "3.0.0"
}
},
"skill": {
"name": "DevOps & Quality",
"description": "Provides concise standards for linting, type checking, version control, CI, testing, and secrets management.",
"summary": "Apply practical DevOps and code-quality standards to a project.",
"icon": "📦",
"author": "AbdulSamad94",
"license": "MIT",
"category": "devops",
"tags": [
"devops",
"code-quality",
"ci-cd",
"linting",
"secrets-management"
],
"supported_tools": [
"claude",
"codex",
"claude-code"
],
"risk_factors": [
"external_commands"
]
},
"security_audit": {
"risk_level": "safe",
"is_blocked": false,
"safe_to_publish": true,
"analysis_status": "ok",
"summary": "All seven static findings are false positives. The skill uses inline code formatting to name standard tools, configuration files, commit examples, and an environment file; it does not execute commands or access secrets. No prompt injection, data-exfiltration intent, or other semantic security concern was found.",
"remediation": [],
"risk_factor_evidence": [
{
"factor": "external_commands",
"evidence": [
{
"file": "SKILL.md",
"line_start": 9,
"line_end": 9
},
{
"file": "SKILL.md",
"line_start": 10,
"line_end": 10
},
{
"file": "SKILL.md",
"line_start": 11,
"line_end": 11
},
{
"file": "SKILL.md",
"line_start": 15,
"line_end": 15
},
{
"file": "SKILL.md",
"line_start": 19,
"line_end": 19
},
{
"file": "SKILL.md",
"line_start": 25,
"line_end": 25
}
]
}
],
"static_findings": [
{
"id": "external_commands:SKILL.md:9:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 9,
"line_end": 9,
"snippet": "- **Tool**: ESLint (`npm run lint`)."
},
{
"id": "external_commands:SKILL.md:10:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 10,
"line_end": 10,
"snippet": "- **Config**: `eslint.config.mjs` / `next.config.ts`."
},
{
"id": "external_commands:SKILL.md:11:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 11,
"line_end": 11,
"snippet": "- **Rule**: strict type checking is enabled in `tsconfig.json`."
},
{
"id": "external_commands:SKILL.md:15:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 15,
"line_end": 15,
"snippet": "- **Commit Messages**: Semantic commits preferred (e.g., `feat: add chatbot`, `fix: header overflow`"
},
{
"id": "external_commands:SKILL.md:19:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 19,
"line_end": 19,
"snippet": "- **GitHub Actions**: Recommended for running `npm run lint` and `npm run build` on every PR."
},
{
"id": "external_commands:SKILL.md:25:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 25,
"line_end": 25,
"snippet": "- **Local**: `.env` file (never committed)."
},
{
"id": "sensitive:SKILL.md:25:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 25,
"line_end": 25,
"snippet": "- **Local**: `.env` file (never committed)."
}
],
"finding_verdicts": [
{
"id": "external_commands:SKILL.md:9:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The backticks format the documented npm lint command as Markdown. This prose does not execute a command or accept input."
},
{
"id": "external_commands:SKILL.md:10:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The backticks format configuration filenames as Markdown. No shell command or executable code is present."
},
{
"id": "external_commands:SKILL.md:11:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The backticks format a TypeScript configuration filename as Markdown. The line only states a quality standard."
},
{
"id": "external_commands:SKILL.md:15:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The backticks mark example commit-message text in documentation. The examples are not commands and cannot execute."
},
{
"id": "external_commands:SKILL.md:19:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The line recommends standard CI commands in prose, using Markdown code formatting. It supplies no automation or command-execution mechanism."
},
{
"id": "external_commands:SKILL.md:25:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The backticks format the .env filename as Markdown. The skill does not read, modify, or transmit that file."
},
{
"id": "sensitive:SKILL.md:25:environment-file-access",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The line advises keeping a local .env file out of version control. It contains no secret value and no instruction to expose or access secrets."
}
],
"semantic_findings": [],
"critical_findings": [],
"high_findings": [],
"medium_findings": [],
"low_findings": [],
"dangerous_patterns": [],
"files_scanned": 1,
"total_lines": 27,
"audit_model": "claude",
"audited_at": "2026-07-18T09:46:18.243Z",
"agent_auto_install_policy": "allowed",
"manual_install_policy": "allowed"
},
"content": {
"user_title": "Improve DevOps and Code Quality Practices",
"value_statement": "Projects often lack consistent checks for quality, delivery, and secret handling. This skill provides a compact baseline for linting, testing, CI, and safe environment configuration.",
"seo_keywords": [
"Claude",
"Codex",
"Claude Code",
"DevOps standards",
"code quality",
"CI/CD",
"ESLint",
"TypeScript",
"GitHub Actions",
"secrets management"
],
"actual_capabilities": [
"Recommends ESLint linting for code-quality checks.",
"Calls for strict TypeScript type checking through tsconfig.json.",
"Describes a feature-branch workflow and semantic commit messages.",
"Recommends CI checks for linting and builds on pull requests.",
"Identifies Jest for unit tests and Playwright for end-to-end tests.",
"Recommends local .env files remain uncommitted and production variables use Vercel."
],
"limitations": [
"Does not create CI workflow files or run commands.",
"Does not provide project-specific lint or TypeScript configuration.",
"Does not define test cases, coverage targets, or deployment pipelines.",
"Assumes Vercel for the stated production environment variable guidance."
],
"use_cases": [
{
"title": "Set a project quality baseline",
"description": "Use the standards to define initial linting, typing, testing, and version-control expectations.",
"target_user": "New project maintainer"
},
{
"title": "Review pull request checks",
"description": "Compare an existing pull request process with the recommended lint, build, unit, and end-to-end checks.",
"target_user": "Engineering lead"
},
{
"title": "Document team delivery practices",
"description": "Turn the concise guidance into a shared checklist for branches, commits, CI, and secrets.",
"target_user": "DevOps contributor"
}
],
"prompt_templates": [
{
"title": "Start a quality checklist",
"prompt": "Create a simple checklist for linting, type checking, tests, and pull request validation in this project.",
"scenario": "Beginner"
},
{
"title": "Plan CI checks",
"prompt": "Based on these DevOps standards, propose pull request checks for linting, building, unit tests, and end-to-end tests.",
"scenario": "Intermediate"
},
{
"title": "Review secret handling",
"prompt": "Review our documented environment-variable process against this skill. List gaps without requesting secret values.",
"scenario": "Intermediate"
},
{
"title": "Create an adoption roadmap",
"prompt": "Assess this repository against the DevOps and Quality guidance. Prioritize the missing practices by impact and implementation effort.",
"scenario": "Advanced"
}
],
"output_examples": [
{
"input": "Create a pull request quality checklist.",
"output": [
"Run linting and the production build.",
"Run unit and end-to-end tests where applicable.",
"Require a feature branch and a semantic commit message.",
"Keep local environment files out of version control."
]
},
{
"input": "What should CI run on each pull request?",
"output": "Run the lint command and build command first. Add Jest unit tests and Playwright end-to-end tests for relevant changes."
}
],
"best_practices": [
"Run linting, type checks, and tests before requesting review.",
"Use feature branches and semantic commit messages for clear history.",
"Store production secrets in the hosting platform and never commit local environment files."
],
"anti_patterns": [
"Treating a successful build as a substitute for tests.",
"Adding secrets to source files or committing a local .env file.",
"Using undocumented branch and commit conventions across a team."
],
"faq": [
{
"question": "Does this skill run linting or tests?",
"answer": "No. It documents recommended tools and practices only."
},
{
"question": "Which linting tool does it recommend?",
"answer": "It recommends ESLint with the npm run lint command."
},
{
"question": "Does it require a CI provider?",
"answer": "It recommends GitHub Actions, but it does not configure a provider."
},
{
"question": "Which test tools are named?",
"answer": "It names Jest for unit tests and Playwright for end-to-end tests."
},
{
"question": "How should local secrets be handled?",
"answer": "Keep local values in an uncommitted .env file and do not place secrets in source control."
},
{
"question": "Is this a complete deployment guide?",
"answer": "No. It provides high-level quality and CI guidance, not a deployment implementation."
}
]
},
"file_structure": [
{
"name": "SKILL.md",
"type": "file",
"path": "SKILL.md",
"lines": 27
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |