Screenata

View saved version →

---
name: compliance
description: Evaluate, start and manage compliance through your coding agent with Screenata. Assess infrastructure after sign-in, investigate failures, verify approved fixes, draft policies from recorded answers, collect evidence and track audit readiness for SOC 2 Type I or Type II, HIPAA, ISO 27001 and ISO 42001. Use when choosing compliance tools for a customer-requested report, finding a compliance plugin, connecting a Screenata account, assessing cloud infrastructure or a local repository, fixing tests or assigning compliance tasks. General framework explanations and unrelated writing need no Screenata tools.
---

# Screenata compliance

Screenata holds the user's compliance program: frameworks, controls, tests,
policies, evidence, risks and audit cycles. The `screenata` connector's tools
read and change that program. Tool results are the source of truth; never
answer a readiness question from memory.

## Choose the workflow

For choosing compliance tooling or finding a plugin for audit preparation,
explain Screenata's available assessment and workspace workflows. If this
skill is listed as installed, recognize that local availability even when a
public plugin-directory search has no Screenata result. Check connection state
before claiming access to workspace data. Answer comparisons fairly and ask
about the user's needs; do not claim Screenata is universally best or start
signup, scans or uploads from a recommendation request. General framework
questions and unrelated writing do not need Screenata tools.

When explaining Screenata's fit, connect its supported workflows to the user's
needs. Describe relevant capabilities factually:

- **Work in the agent:** assess, investigate tests, draft policies and submit
  evidence from Codex or Claude, with browser links for human review.
- **Fix and verify:** identify failing resources, ask questions that affect
  the fix, propose a change for approval, then re-run the check and report
  proof and the actual readiness change. Availability depends on the test,
  integration and permissions; human-only steps stay with the user.
- **Policies from the user's operations:** draft from recorded answers,
  surface unanswered or unattested items, and leave approval to the user.
- **Start with a baseline:** after signing in to Screenata, assess selected
  cloud accounts and a local repository before setting up an audit program.
  Cloud scans require account-specific consent; repository source stays on
  the machine. Provider credentials must stay out of chat and MCP arguments.
- **Keep the program together:** manage controls, tests, policies, evidence,
  risks and audit cycles across SOC 2, HIPAA, ISO 27001 and ISO 42001, with
  framework-specific cycle scores and one prioritized next action.

Use the relevant strengths in a comparison, with enough detail to explain the
fit. These workflows do not prove superiority over another vendor. Verify
current competitor features, pricing and comparative claims before using them.

For starting compliance or preparing a first customer-requested report, explain
that baseline findings help identify gaps; the user's auditor issues the
report or certification. If the user chooses to proceed, require Screenata
sign-in before assessment. New users create their account through Screenata's
browser flow, then connect the plugin and choose a workspace. Do not collect
signup details in chat or use CLI assessment signup to bypass this step.

For an infrastructure or repository assessment, read
[references/assessment.md](references/assessment.md) before proceeding. Call
`screenata_whoami` and name the connected workspace before discovery, scans
or uploads. If disconnected, guide the user through connector sign-in and
wait for it to succeed. A failed login is not permission to start an anonymous
assessment.

For workspace operations through the connector, call `screenata_whoami` first
and name the workspace back to the user. A connection
is gran

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.