Agent skill · Security

soc2-readiness

Assess SOC 2 readiness across the Trust Services Criteria and produce a gap remediation plan. Use when asked to prepare for a SOC 2 audit, run a SOC 2 readiness/gap assessment, scope controls, or get audit-ready. Produces a readiness report — scope & criteria, a control-by-control status, a weighted readiness score, prioritised gaps with owners, and the evidence each control needs.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorships scriptsMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill soc2-readiness --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: yes
Path: skills/soc2-readiness/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# SOC 2 Readiness Skill A SOC 2 audit fails on two things: missing controls and missing *evidence* of controls you actually run. This skill scopes the engagement to the right Trust Services Criteria, assesses each control's status honestly, scores readiness deterministically (so "we're basically ready" becomes a number), and turns the gaps into a prioritised, owned remediation plan with the evidence each control must produce. ## Required Inputs Ask for these only if they aren't already provided: - **Report type & period** — SOC 2 Type I (point in time) or Type II (a window, usually 3–12 months). - **In-scope criteria** — Security (always), plus any of Availability, Confidentiality, Processing Integrity, Privacy. Don't include criteria you can't evidence. - **Systems in scope** — the product/infra boundary the report covers. - **Current control state** — what's implemented, partially implemented, or missing (be honest; auditors test, they don't take your word). ## Output Format ### SOC 2 Readiness: [company] — [Type I/II], [period] **1. Scope** — the systems, the in-scope criteria, and explicitly what's out of scope. **2. Control status** — a table grouped by criterion; status is `m

What's inside
Steps it walks through
  1. Required Inputs
  2. Output Format
  3. SOC 2 Readiness: [company] — [Type I/II], [period]
  4. Programmatic Helper
  5. Quality Checks
  6. Anti-Patterns
  7. Based On
Ships with 1 file
  • scripts/soc2_score.py
Commands it runs
python3 scripts/soc2_score.py controls.json
python3 scripts/soc2_score.py controls.json --json   # machine-readable, for chaining
More from pm-claude-skills
All skills →
About this skill
What does the soc2-readiness skill do?

Assess SOC 2 readiness across the Trust Services Criteria and produce a gap remediation plan. Use when asked to prepare for a SOC 2 audit, run a SOC 2 readiness/gap assessment, scope controls, or get audit-ready. Produces a readiness report — scope & criteria, a control-by-control status, a weighted readiness score, prioritised gaps with owners, and the evidence each control needs.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill soc2-readiness --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going