compliance evidence collector
- Repo stars 1
- Author repo claude-skills
- Domain
- Security
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @00PrabalK00 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Compliance Evidence Collector
## Overview
Gather code, config, docs, and operational proof points for audits and internal compliance reviews.
## Core Workflow
1. Survey the relevant files, configs, runtime signals, or artifacts to identify the important components and boundaries.
2. Map the relationships, dependencies, or graph structure that explain how the system or corpus fits together.
3. Highlight missing links, risky assumptions, or ambiguous edges that affect understanding or change safety.
4. Return a concise map plus the next best checks or follow-up actions.
## Deliver
- A structured map of components, dependencies, or graph relationships.
- The highest-risk gaps, missing links, or ambiguous edges.
- Concrete next checks or actions based on the mapped structure.
## Guardrails
- Do not infer strong relationships without evidence from code, config, or runtime artifacts.
- Separate confirmed connections from plausible but unverified ones.
- Prefer a smaller high-confidence map over a speculative complete one.
- Do not invent metrics, policy decisions, customer commitments, or ownership that the inputs do not support.
Sections and files
Listed in source order.
sections -> Overview → Core Workflow → Deliver → Guardrails
terms -> Gather code, config, docs, and operational proof points for audits and internal compliance reviews. · 1. Survey the relevant files, configs, runtime signals, or artifacts to identify the important components and boundaries. · - A structured map of components, dependencies, or graph relationships. · - Do not infer strong relationships without evidence from code, config, or runtime artifacts.
files/cmd -> no explicit files or commands
body sha256 -> 15c37442d5eb
Core Workflow
Survey the relevant files, configs, runtime signals, or artifacts to identify the important components and boundaries. Map the relationships, dependencies, or graph structure that explain how the system or corpus fits together. Highlight missing links, risky assumptions, or ambiguous edges that affect understanding or change safety. Return a concise map plus the next best checks or follow-up actions.
Deliver
A structured map of components, dependencies, or graph relationships. The highest-risk gaps, missing links, or ambiguous edges. Concrete next checks or actions based on the mapped structure.
Guardrails
Do not infer strong relationships without evidence from code, config, or runtime artifacts. Separate confirmed connections from plausible but unverified ones. Prefer a smaller high-confidence map over a speculative complete one. Do not invent metrics, policy decisions, customer commitments, or ownership that the inputs do not support.