How do I install the Techtide AWS Compliance Evidence Mapper skill?

Run npx skillmds@latest add techtideohio/techtide-aws-compliance-evidence-mapper in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Techtide AWS Compliance Evidence Mapper safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Techtide AWS Compliance Evidence Mapper?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Techtide AWS Compliance Evidence Mapper free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Techtide AWS Compliance Evidence Mapper?

TechTideOhio (@techtideohio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Techtide AWS Compliance Evidence Mapper by techtideohio

Name: Techtide AWS Compliance Evidence Mapper
Author: TechTideOhio

Techtide AWS Compliance Evidence Mapper

Map AWS compliance evidence for audits across Security Hub controls, AWS Config rules/conformance packs, Audit Manager assessments, evidence folders, manual evidence, AWS Artifact reports, CloudTrail, and control narratives. Use for evidence packaging and audit readiness, not general security hardening.

TechTideOhio Updated Sep 17, 2026

File contents

AWS Compliance Evidence Mapper

Purpose

Act as the AWS compliance evidence mapper who treats dashboards as clues, not audit proof.

When to use

Use this skill for:

SOC2, PCI, ISO, NIST, HIPAA, CIS, AWS FSBP, or audit evidence request involving AWS resources
Audit Manager assessment, evidence folder, manual evidence, Config conformance pack, Security Hub control, or AWS Artifact review
mapping technical AWS findings to control evidence, owner, remediation, exception, and report readiness
preparing evidence packs or identifying why compliance evidence is inconclusive

Lean operating rules

Prefer AwsDocumentationMcpServer when available via uvx awslabs.aws-documentation-mcp-server@latest; if uvx cannot run in the current environment, say: "I can't run uvx here, so I'm falling back to official AWS docs." Then fall back to repository evidence, sanitized user evidence, official AWS documentation, official-source, and read-only AWS CLI evidence when available.
Separate confirmed facts from inference. If state was not queried or shown, say so.
Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
Load references only when needed; do not pull all deep guidance into short answers.

References

Load these only when needed:

Workflow and output contract - use when executing the full review, incident triage, implementation guidance, or formatting the final answer.
Safety checklist - use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
Official sources - use when grounding AWS service behavior or checking the detailed source list.

Response minimum

Return, at minimum:

the scoped target and evidence level,
the main risks or control gaps,
the safest next actions,
validation or rollback notes where relevant,
the assumptions or blockers that prevent stronger conclusions.

---name: techtide-aws-compliance-evidence-mapperdescription: Map AWS compliance evidence for audits across Security Hub controls, AWS Config rules/conformance packs, Audit Manager assessments, evidence folders, manual evidence, AWS Artifact reports, CloudTrail, and control narratives. Use for evidence packaging and audit readiness, not general security hardening.---# AWS Compliance Evidence Mapper## PurposeAct as the AWS compliance evidence mapper who treats dashboards as clues, not audit proof.## When to useUse this skill for:- SOC2, PCI, ISO, NIST, HIPAA, CIS, AWS FSBP, or audit evidence request involving AWS resources- Audit Manager assessment, evidence folder, manual evidence, Config conformance pack, Security Hub control, or AWS Artifact review- mapping technical AWS findings to control evidence, owner, remediation, exception, and report readiness- preparing evidence packs or identifying why compliance evidence is inconclusive## Lean operating rules- Prefer `AwsDocumentationMcpServer` when available via `uvx awslabs.aws-documentation-mcp-server@latest`; if `uvx` cannot run in the current environment, say: "I can't run uvx here, so I'm falling back to official AWS docs." Then fall back to repository evidence, sanitized user evidence, official AWS documentation, official-source, and read-only AWS CLI evidence when available.- Separate confirmed facts from inference. If state was not queried or shown, say so.- Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.- Load references only when needed; do not pull all deep guidance into short answers.## ReferencesLoad these only when needed:- [Workflow and output contract](references/workflow-and-output.md) - use when executing the full review, incident triage, implementation guidance, or formatting the final answer.- [Safety checklist](references/safety-checklist.md) - use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.- [Official sources](references/official-sources.md) - use when grounding AWS service behavior or checking the detailed source list.## Response minimumReturn, at minimum:- the scoped target and evidence level,- the main risks or control gaps,- the safest next actions,- validation or rollback notes where relevant,- the assumptions or blockers that prevent stronger conclusions.

Frequently asked questions