Skip to main content
Agent skill

Secureframe

Read a team's Secureframe compliance posture: failing tests and what to remediate for SOC 2, ISO 27001, HIPAA, PCI or GDPR.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Secureframe when an AI agent needs a reusable SKILL.md workflow for this job: Read a team's Secureframe compliance posture: failing tests and what to remediate for SOC 2, ISO 27001, HIPAA, PCI or GDPR.

When not to use it

Skip Secureframe when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/secureframe
# Save SKILL.md to ~/.claude/skills/secureframe/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/secureframe/SKILL.md. For a shared project, commit the folder at .claude/skills/secureframe/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Secureframe skill for this task: Use Secureframe when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

69/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
72/100
Practical detail
68/100
Source evidence
63/100
Source signals
70/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Secureframe compliance

Use this skill when the user wants to know which compliance checks are failing or what needs remediating for their security frameworks (SOC 2, ISO 27001, HIPAA, PCI, GDPR) as tracked by Secureframe.

The Secureframe API key/secret is held **server-side** by Nuphos. You never handle it — read everything through the Nuphos API with `ac`. Do not ask the user for Secureframe credentials, and do not paste them into chat.

## Discovering the integration

The enabled credentials prompt lists each Secureframe integration with its `integrationId` and a `testsEndpoint`. If none is listed, ask the user to bind a Secureframe integration and enable it for this session — do not conclude Secureframe is unsupported.

## Reading failing tests (the issues to fix)

Each Secureframe *test* is one compliance check. The list route wraps results in an object, so extract `.tests[]` before piping to `jq`:

```bash # Default: failing tests (health_status:fail — the compliance issues to resolve) ac /teams/<teamId>/secureframe-integrations/<integrationId>/tests # -> { "tests": [...] }

# All tests (not just failing): ac "/teams/<teamId>/secureframe-integrations/<integrationId>/tests?failingOnly=false"

# Custom Lucene filter (Secureframe query syntax): ac "/teams/<teamId>/secureframe-integrations/<integrationId>/tests?q=health_status:fail%20AND%20frameworks:soc2_alpha" ```

Each test carries:

```bash ac /teams/<teamId>/secureframe-integrations/<integrationId>/tests \ | jq -r '.tests[] | "[\(.healthStatus)] \(.description)\n why: \(.failureMessage)\n fix: \(.remediation)\n"' ```

Fields: `id`, `description`, `healthStatus` (`pass`/`fail`/`disabled`), `enabled`, `failureMessage` (why it's failing), `remediation` (how to fix it), and `raw` (the full attributes blob for anything not normalized — e.g. `framework_keys`, `test_domain`, `last_passed_at`).

## How to help

- Summarize failing tests; lead with what maps to infrastructure the user can act on. - When a failing test maps to a resource reachable through another bound provider (AWS config, Cloudflare setting, GitHub finding), offer to remediate it there — but confirm with the user before any change.

## Safety

- Read-only. This skill only reads compliance status; it never writes to Secureframe. - Never print or echo the Secureframe API key/secret (reads go through the Nuphos API above, which keeps them server-side).

Intended uses

  • Use Secureframe when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.