agentsclimarketplace

Supply chain security

Skill bromso/metapowers/plugins/security/skills/supply-chain-security

A Claude Code plugin that adds an agentic skills framework, with MCP's and a meta prompting processes. Inspired by "Superpowers" & "Figma Console MCP", but not just for development or design; but for all aspect within the digital production cycle.

Install
npx -y skills add bromso/metapowers --skill supply-chain-security

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

  • 1 stars1 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.

What its author says it does

Copied from the file, not written here

Assess and manage third-party and supply chain security risks

SKILL.md

3.8 KB, as published. Nobody here has run it

Supply Chain Security

Assess and manage third-party and supply chain security risks for "$ARGUMENTS". Inventory vendors and dependencies, evaluate their security posture, and establish ongoing monitoring practices.

Prerequisites

None — this is a Phase 0 Govern skill.

Process

  1. Inventory third-party vendors and dependencies:

    • Enumerate all third-party relationships: SaaS providers, cloud services, open-source libraries, contractors, managed service providers, payment processors
    • For each vendor/dependency, document: name, purpose, contract status, data shared, integration type (API, SDK, data feed, physical access)
    • Include both direct vendors and transitive dependencies (vendors of vendors where known)
  2. Assess each by criticality and data access:

    • Criticality rating — what happens if this vendor is unavailable or compromised?
      • Critical: business stops, customer data exposed
      • High: significant operational impact, sensitive data at risk
      • Medium: degraded capability, internal data exposure
      • Low: minimal impact, no sensitive data
    • Data access classification — what data does the vendor access, process, or store?
    • Integration depth — how deeply embedded is the vendor in operations?
  3. Evaluate vendor security posture:

    • Review available evidence per vendor:
      • Certifications — SOC 2 Type II, ISO 27001, PCI DSS, FedRAMP
      • Security questionnaires — SIG, CAIQ, or custom questionnaire responses
      • Penetration test reports — third-party test results and remediation status
      • Incident history — known breaches, response quality, disclosure transparency
      • Security policies — published security practices and commitments
    • Score each vendor's posture: Strong, Adequate, Weak, Unknown
  4. Define vendor security requirements:

    • Establish minimum security requirements by vendor tier:
      • Critical vendors: SOC 2 Type II, annual pen test, incident notification SLA, right to audit
      • High vendors: SOC 2 or equivalent certification, security questionnaire, incident notification
      • Medium vendors: security questionnaire, data processing agreement
      • Low vendors: standard terms review, basic security assessment
    • Define contractual security clauses to include in vendor agreements
  5. Create vendor risk tiers:

    • Combine criticality, data access, and security posture into an overall risk tier
    • Assign each vendor to a tier (Tier 1: highest risk, Tier 4: lowest risk)
    • Define management activities per tier (review frequency, monitoring depth, escalation procedures)
    • Identify vendors requiring immediate risk remediation
  6. Write the artifact to .metapowers/security/$ARGUMENTS/00-govern.md with heading:

    Supply Chain Security Assessment

    Include sections:

    • Vendor Inventory — complete list with purpose, data access, and integration type
    • Criticality Assessment — criticality and data classification per vendor
    • Security Posture Evaluation — evidence reviewed and posture score per vendor
    • Vendor Risk Tiers — tier assignment with rationale
    • Security Requirements — minimum requirements by tier
    • Monitoring Plan — ongoing assessment schedule and triggers for re-evaluation

Output

The supply chain security assessment written to .metapowers/security/$ARGUMENTS/00-govern.md. Present a summary to the user highlighting:

  • Total vendors inventoried and distribution across risk tiers
  • Vendors with weak or unknown security posture requiring attention
  • Critical vendors and their current compliance status
  • Recommended immediate actions for highest-risk vendors

Keep looking

Skills are one crate of 328,083. 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.