skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
netresearch/enterprise-readiness-skill79 installs

enterprise-readiness

Use when evaluating projects for production or enterprise readiness, implementing supply chain security (SLSA, cosign, SBOMs, pnpm), hardening CI/CD pipelines, establishing quality gates (TYPO3: CI matrix PHP 8.2-8.5 x TYPO3 12.4/13.4/14.3 LTS), pursuing OpenSSF Best Practices Badge (Passing/Silver/Gold) or OSPS Baseline levels, reviewing code quality, writing ADRs, or configuring Git hooks and CI pipelines.

How do I install this agent skill?

npx skills add https://github.com/netresearch/enterprise-readiness-skill --skill enterprise-readiness
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The enterprise-readiness skill is a professional security auditing and project hardening toolkit. It enables AI agents to evaluate repositories against enterprise standards, implement supply chain security (SLSA, cosign, SBOMs), and automate OpenSSF Best Practices compliance. The skill utilizes deterministic auditing scripts and interacts only with well-known security platforms. No malicious patterns or security vulnerabilities were identified.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerfail

    29/40 files flagged

  • ZeroLeakspass

    Score: 93/100 · 2 sections analyzed

What does this agent skill do?

Enterprise Readiness Assessment

Production/enterprise tier only — see references/tier-framing.md.

When to Use

  • Production/enterprise readiness evaluations
  • Supply chain security: SLSA provenance, cosign signing, SBOMs
  • CI/CD hardening, workflow permissions
  • OpenSSF Best Practices (Passing/Silver/Gold), OSPS Baseline (L1/2/3)
  • Scorecard optimization (Token-Permissions, Branch-Protection, Pinned-Deps)
  • Code review, ADRs, changelogs, SECURITY.md

Assessment Workflow

  1. Discovery: Identify platform, languages, existing CI/CD, dependabot.yml; check the required root .bestpractices.json for maintained public projects (scope and validation: references/bestpractices-json.md, ER-74/ER-75).
  2. Scoring: Apply checklists; check Scorecard, badge criteria, coverage
  3. Gap Analysis: List missing controls by severity
  4. Implementation: Apply fixes (SHA-pin actions, harden permissions, add workflows)
  5. Verification: Re-score and compare

Mandatory Workflows & Badges

Required coverage: CI, CodeQL, Scorecard, dependency review, composer audit, SBOM — as dedicated workflows or jobs calling the netresearch reusable. Badges: CI, Codecov, Scorecard, Best Practices, Baseline. See references/badges-and-workflows.md.

Maintained public projects MUST include an evidence-backed .bestpractices.json at the repository root, even before badge registration. Create or refresh it from the project's own evidence; omit unknowns. The file proposes answers and does not register a project, save the questionnaire or award a badge. See references/bestpractices-json.md.

Key Hardening Patterns

  • Permissions: Declare permissions: contents: read at workflow-level; grant write only per-job
  • SHA pinning: Third-party actions pinned to SHA with version comment (# v4.2.0). Org-internal reusable workflows use @main
  • Harden-Runner: step-security/harden-runner as first step in every job; prefer egress-policy: block with allowed-endpoints
  • Dependabot: Configure dependabot.yml with all ecosystems (composer, npm, github-actions, docker); set up auto-merge workflow for dependency PRs using pull_request_target
  • Coverage: Upload via codecov-action; configure codecov.yml with patch coverage threshold
  • Duplicate CI prevention: Scope push: trigger to branches: [main] when pull_request: is also present
  • SLSA provenance: Use actions/attest-build-provenance with id-token: write and attestations: write permissions; verify with gh attestation verify. That is Level 2 in the project's own workflow; Level 3 needs checkout, build and attestation all inside one org reusable the project cannot edit — see references/slsa-provenance.md
  • Security policy: Create SECURITY.md with vulnerability disclosure process and response SLA (Critical: 7 days, High: 30 days)

Critical Rules

  • NEVER interpolate ${{ github.event.* }} or ${{ inputs.* }} in run: blocks (script injection)
  • NEVER guess action versions -- fetch from GitHub API and verify SHA against tags
  • ALWAYS include https:// URLs in badge justifications
  • ALWAYS configure auto-merge for repos with Dependabot/Renovate

References

ReferenceUse
references/general.mdAlways
references/scorecard-playbook.mdScorecard optimization
references/badges-and-workflows.mdBadge URLs, workflows
references/mandatory-requirements.mdChecklist
references/ci-patterns.mdCI/CD, hooks
references/code-review.mdPR quality and verification claims
references/slsa-provenance.mdSLSA Level 3
references/signed-releases.mdCosign/GPG
references/openssf-badge-silver.mdSilver
references/openssf-badge-gold.mdGold
references/openssf-badge-baseline.mdOSPS Baseline
references/bestpractices-json.md.bestpractices.json: pre-fill badge answers from the repo
references/harden-runner-guide.mdHarden-Runner
references/solo-maintainer-guide.mdSolo-maintainer criteria
references/npm-pnpm-supply-chain.mdpnpm, npm ci, npx, lockfile, Node tooling in a CI job (Sonar S8543/S6505, CodeQL path-injection)
references/python-pip-supply-chain.mdpip

Related skills: go-development, github-project, security-audit, git-workflow.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/netresearch/enterprise-readiness-skill/enterprise-readiness">View enterprise-readiness on skillZs</a>