build-a-controls-evidence-map

Connect control claims to owners, systems, tests, and current evidence. Use when assurance, audits, customer reviews, governance, or risk decisions require proof that controls are designed and operating.

Ir para a instalação

Repositório: protosphinx/sphinxstack
Última atividade na origem: 29 de julho de 2026 às 13:55
Idioma detectado do SKILL.md: inglês
Estrelas: 1
Forks: 0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/protosphinx/sphinxstack --skill build-a-controls-evidence-map

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

2 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

assign-material-and-check-mass-in-partmode

Assign materials to PartMode bodies and verify revision-bound volume, mass, center of mass, inertia, and geometry health. Use when someone asks how much a part or assembly weighs, needs density-driven properties, or sees an incomplete mass result.

2026-08-08

connect-partmode-to-an-agent

Configure and verify PartMode's hosted MCP server for a person's agent without exposing credentials or granting more CAD authority than needed. Use when they say "connect PartMode to Codex," "set up PartMode MCP," "add PartMode to my agent," or ask why the PartMode MCP URL does not behave like a normal web page.

2026-08-08

create-a-drawing-in-partmode

Generate and verify an exact projected PartMode drawing from a settled part, assembly, or configuration. Use when someone asks for a drawing sheet, SVG, DXF, or PDF output, standard views, dimensions, notes, or a reviewable manufacturing document.

2026-08-08

Ver todas deste repositório

build-a-controls-evidence-map

Make control claims testable. Policy text can support intent, but operating effectiveness needs evidence from the systems and people performing the control.

Procedure

Define framework, scope, period, entities, environments, assertion owner, and intended audience.

Normalize overlapping requirements into control objectives without losing source traceability.

For each objective, document risk, control activity, frequency, population, performer, reviewer, and enforcement point.

Distinguish manual, automated, inherited, complementary, detective, preventive, and compensating controls.

Attach evidence sources with period, collection method, owner, retention, sensitivity, and integrity checks.

Define design and operating tests, including sample logic and exception handling.

Reconcile claimed populations to authoritative inventories before selecting samples.

Mark evidence as current, stale, incomplete, contradictory, planned, or unavailable.

Track gaps to remediation or time-bounded risk acceptance; never backdate missing performance.

Refresh the map after scope, system, owner, control, or requirement changes.

Guardrails

Do not claim compliance merely because every requirement has a row.

Protect credentials, personal data, security findings, and vendor confidential material.

Screenshots need source, date, scope, and corroboration where state can change.

Separate evidence collection from independent evaluation when assurance rules require it.

Done

Requirements retain source-to-control traceability

Control populations, owners, tests, and evidence are explicit

Stale, missing, and conflicting proof remains visible

Remediation and risk acceptance are auditable

name	build-a-controls-evidence-map
category	data
description	Connect control claims to owners, systems, tests, and current evidence. Use when assurance, audits, customer reviews, governance, or risk decisions require proof that controls are designed and operating.