home / skills / questnova502 / claude-skills-sync / enterprise-readiness

This skill assesses enterprise readiness of Python projects and guides security, SBOMs, signing, and CI/CD hardening for production-grade software.

npx playbooks add skill questnova502/claude-skills-sync --skill enterprise-readiness

Review the files below or copy the command above to add this skill to your agents.

Files (28)
SKILL.md
4.3 KB
---
name: enterprise-readiness
description: "Assess and enhance software projects for enterprise-grade security, quality, and automation. Use when evaluating projects for production readiness, implementing supply chain security (SLSA, signing, SBOMs), hardening CI/CD pipelines, or establishing quality gates. Aligned with OpenSSF Scorecard, Best Practices Badge (all levels), SLSA, and S2C2F. By Netresearch."
---

# Enterprise Readiness Assessment

## When to Use

- Evaluating projects for production/enterprise readiness
- Implementing supply chain security (SLSA, signing, SBOMs)
- Hardening CI/CD pipelines
- Establishing quality gates
- Pursuing OpenSSF Best Practices Badge (Passing/Silver/Gold)

## Assessment Workflow

1. **Discovery**: Identify platform (GitHub/GitLab), languages, existing CI/CD
2. **Scoring**: Apply checklists from references based on stack
3. **Badge Assessment**: Check OpenSSF criteria status
4. **Gap Analysis**: List missing controls by severity
5. **Implementation**: Apply fixes using scripts and templates

## Reference Files (Load Based on Stack)

| Reference | When to Load |
|-----------|--------------|
| `references/general.md` | Always (universal 60 pts) |
| `references/github.md` | GitHub-hosted projects (40 pts) |
| `references/go.md` | Go projects (20 pts) |
| `references/openssf-badge-silver.md` | Pursuing Silver badge |
| `references/openssf-badge-gold.md` | Pursuing Gold badge |

## Implementation Guides

| Guide | Purpose |
|-------|---------|
| `references/quick-start-guide.md` | Getting started |
| `references/dco-implementation.md` | DCO enforcement |
| `references/signed-releases.md` | Cosign/GPG signing |
| `references/reproducible-builds.md` | Deterministic builds |
| `references/security-hardening.md` | TLS, headers, validation |
| `references/solo-maintainer-guide.md` | N/A criteria justification |
| `references/branch-coverage.md` | Gold 80% branch coverage |

## Automation Scripts

| Script | Purpose |
|--------|---------|
| `scripts/verify-badge-criteria.sh` | Verify OpenSSF badge criteria |
| `scripts/check-coverage-threshold.sh` | Statement coverage check |
| `scripts/check-branch-coverage.sh` | Branch coverage (Gold) |
| `scripts/add-spdx-headers.sh` | Add SPDX headers (Gold) |
| `scripts/verify-signed-tags.sh` | Tag signature verification |
| `scripts/verify-review-requirements.sh` | PR review requirements |

## Document Templates

Templates in `assets/templates/`:
- `GOVERNANCE.md` - Project governance (Silver)
- `ARCHITECTURE.md` - Technical docs (Silver)
- `CODE_OF_CONDUCT.md` - Contributor Covenant
- `SECURITY_AUDIT.md` - Security audit (Gold)
- `BADGE_EXCEPTIONS.md` - N/A justifications

## CI Workflow Templates

GitHub Actions workflows in `assets/workflows/`:

| Workflow | Purpose |
|----------|---------|
| `scorecard.yml` | OpenSSF Scorecard security analysis |
| `codeql.yml` | Semantic code security scanning |
| `dependency-review.yml` | PR dependency CVE/license check |
| `slsa-provenance.yml` | SLSA Level 3 build attestation |
| `dco-check.yml` | Developer Certificate of Origin |

Copy workflows to `.github/workflows/` and pin action versions with SHA hashes.

## Scoring Interpretation

| Score | Grade | Status |
|-------|-------|--------|
| 90-100 | A | Enterprise Ready |
| 80-89 | B | Production Ready |
| 70-79 | C | Development Ready |
| 60-69 | D | Basic |
| <60 | F | Not Ready |

## Critical Rules

- **NEVER** interpolate `${{ github.event.* }}` in `run:` blocks (script injection)
- **NEVER** guess action versions - always fetch from GitHub API
- **ALWAYS** use SHA pins for actions with version comments
- **ALWAYS** verify commit hashes against official tags

## Related Skills

| Skill | Purpose |
|-------|---------|
| `go-development` | Go code patterns, Makefile interface, testing |
| `github-project` | Repository setup, branch protection, auto-merge |
| `security-audit` | Deep security audits (OWASP, XXE, SQLi) |
| `git-workflow` | Git branching, commits, PR workflows |

## Resources

- [OpenSSF Scorecard](https://securityscorecards.dev/)
- [Best Practices Badge](https://www.bestpractices.dev/)
- [SLSA Framework](https://slsa.dev/)
- [S2C2F](https://github.com/ossf/s2c2f)

---

> **Contributing:** Improvements to this skill should be submitted to the source repository:
> https://github.com/netresearch/enterprise-readiness-skill

Overview

This skill assesses and enhances software projects for enterprise-grade security, quality, and automation. It provides checklists, templates, and scripts to evaluate production readiness and implement supply chain protections aligned with OpenSSF, SLSA, and Best Practices Badge guidance. Use it to produce a scored readiness report and prioritized remediation plan.

How this skill works

The skill discovers project metadata (platform, languages, CI) and runs stack-specific checklists to compute a readiness score. It maps findings to OpenSSF Badge criteria, performs a gap analysis by severity, and provides automation playbooks and workflow templates to remediate issues. Scripts and templates speed implementation for SBOMs, signing, CI hardening, and quality gates.

When to use it

  • Before promoting a project to production or enterprise distribution
  • When implementing supply chain security: SLSA, signed releases, SBOMs
  • To harden CI/CD pipelines and enforce developer controls
  • When pursuing OpenSSF Best Practices Badge (passing/silver/gold)
  • To establish automated quality gates and coverage thresholds

Best practices

  • Discover platform and CI first to load relevant references and workflows
  • Use SHA-pinned GitHub Actions and verify commit hashes from the API
  • Avoid interpolating runtime event variables in run: blocks to prevent script injection
  • Automate verification (badge checks, coverage, signed tags) with provided scripts
  • Document governance, architecture, and security decisions with provided templates

Example use cases

  • Run a readiness scan to get an A–F grade and a prioritized remediation list
  • Integrate SLSA provenance and cosign signing into existing CI for release integrity
  • Adopt templates and workflows to meet Silver/Gold Best Practices Badge requirements
  • Add automated checks for SPDX headers, branch coverage, and PR review rules
  • Harden a mono-repo CI pipeline by pinning actions and enforcing secure secrets handling

FAQ

What score indicates enterprise readiness?

A score of 90–100 (grade A) indicates enterprise-ready; 80–89 is production-ready.

Can I use the workflows on GitLab?

Workflows are provided as GitHub Actions; adapt CI steps and scripts to GitLab CI or other runners as needed.