mcpField
T
trust-center-readiness-review

trust-center-readiness-review

github.com/sylphxaiSecurity141 installsUpdated today
Repository

About trust-center-readiness-review

A skill for converting trust-center and security-assurance questions into a plan for claims, evidence, owners, and review processes. It supports teams preparing public security information and enterprise sales materials.

Key features

  1. 01Classifies trust-center surfaces
  2. 02Sets claim and evidence boundaries
  3. 03Plans evidence requests and access
  4. 04Assigns owners and update triggers
  5. 05Creates review and evidence checklists

Use cases

  1. 01Preparing a public security overview
  2. 02Organizing gated compliance evidence
  3. 03Reviewing sales security claims

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill trust-center-readiness-review

After installing, type/trust-center-readiness-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/trust-center-readiness-patterns.md

Details

From the project README

Trust Center Readiness Review

Use this skill to convert a trust centers, public security/privacy proof, compliance evidence, subprocessors, uptime, and sales assurance question into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify buyer segment, trust objections, claims, evidence sources, policy owners, compliance status, subprocessor exposure, and sales/security questionnaire needs.
  2. Read references/trust-center-readiness-patterns.md.
  3. Classify trust-center surface: public overview, gated evidence room, security questionnaire support, compliance portal, status/uptime hub, or enterprise sales enablement.
  4. Define claim-proof boundaries, policy library, evidence request workflow, owner cadence, update triggers, access controls, and sales/support handoffs.
  5. Produce trust center plan, state machine, decision table, event schema, evidence checklist, and stale-claim review loop.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not publish certifications, audits, SLAs, encryption claims, or subprocessors without current evidence and owner approval.
  • Do not expose sensitive architecture, pentest, customer, or incident details in public trust pages.
  • Do not let sales use trust-center claims that are broader than the published evidence.
  • Do not keep stale subprocessors, policies, screenshots, or compliance status visible after changes.

Output format

Trust center context:
Buyer / claim / evidence / public-private boundary:

Trust center plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Claims, evidence, and owners:
- <item> -> <policy, metric, edge case, support note>

Stale-claim and evidence-request handling:
- <trigger> -> <action, communication, owner>

Comments

Markdown supported