agentsclimarketplace

Spec security analysis

Skill agent-ix/quoin/skills/spec-security-analysis

Analyze specifications and implementations to identify applicable security standards and generate compliance traceability documentation.From its SKILL.md

Install
npx -y skills add agent-ix/quoin --skill spec-security-analysis

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

One thing to look at

  • 20 stars20 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

4.2 KB, as published. Nobody here has run it

Security Compliance Analysis

Analyze a component's specification and implementation to generate comprehensive security compliance traceability. Apply ALL security standards for maximum coverage - overlapping controls strengthen rather than conflict.

Mandatory Standards

Apply ALL of these standards to EVERY analysis (scope varies by component function):

StandardVersionScope
AICPA SOC 22017 TSCTrust Services Criteria
ISO/IEC 270012022Annex A Controls
NIST SP 800-53Rev 5.2.0Security & Privacy Controls
OWASP ASVS5.0.0Application Security Verification
EU GDPR2016/679Data Protection Articles

Process

  1. Gather Context

    • Read spec/spec.md (if exists)
    • Scan implementation for security-relevant patterns (auth, data, API, logging)
    • Identify component type and function
  2. Identify Applicable Controls

  3. Map Controls to Requirements

    • Link each applicable control to existing FR/NFR/StR requirements
    • Identify gaps where controls lack requirement coverage
    • Document requirement-to-control bidirectional traceability
  4. Define Scope Boundaries

    • Identify controls outside component scope
    • Assign responsible component for out-of-scope controls
    • Document explicitly what is NOT covered and why
  5. Generate Output

Output Sections

  • 19.1 Targeted Standards: All 5 mandatory standards with version and scope
  • 19.2 Control Mapping: Control ID → Standard → Name → Component Requirement
  • 19.3 GDPR Compliance: Specific GDPR article coverage
  • 19.4 Audit Support Controls: Cross-standard audit and logging controls
  • 19.5 Out of Scope: Controls outside component boundary with responsible component

Rules

  • Apply ALL standards - comprehensive coverage trumps minimal compliance
  • Every control mapping MUST reference specific FR/NFR/StR identifiers
  • Overlapping controls from multiple standards reinforce coverage
  • Out-of-scope controls MUST identify the responsible component
  • Gap identification is required - missing control coverage is a finding

References

Keep looking

Skills are one crate of 611,919. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.