- Home
- Skills
- DevOps & Cloud
- SecretMap — CI Variable Reference Audit
More screenshots
Works with the AI Agents you already use
SecretMap — CI Variable Reference Audit
Find undefined, shadowed and inconsistent secret names in CI and deployment configuration without reading secret values.
$5
SecretMap — CI Variable Reference Audit
Example session with this skill installed
Run SecretMap — CI Variable Reference Audit as an evidence-first preflight. This is a representative, hypothetical test case: preview.yml references secrets.CRON_SECRET while the supplied inventory contains PREVIEW_CRON_SECRET only. The materials I have available are: GitHub Actions YAML; variable-name inventory with no values; environment names and deployment notes. Tell me what is evidenced, what is missing, which claims must be held, the exact corrections, and a clean verification plan. Do not claim you opened a file or performed a live run unless one is actually supplied.
- Read your context and instructions
- Compiled the secretmap
REPRESENTATIVE EXAMPLE — NOT A LIVE RUN
PREFLIGHT: HOLD / VERIFY BEFORE ACTING. Task: Find undefined, shadowed and inconsistent secret names in CI and deployment configuration without reading secret values.
Scenario supplied by buyer: preview.yml references secrets.CRON_SECRET while the supplied inventory contains PREVIEW_CRON_SECRET only.
-
MATERIAL FINDING (HIGH): The workflow and inventory contain mismatched names; the underlying values were not accessed. The case describes a potential issue; no underlying account, file or production service has been accessed by this illustrative demo.
-
TRACEABILITY MATRIX
- Claimed behavior: preview.yml references secrets.CRON_SECRET while the supplied inventory contains PREVIEW_CRON_SECRET only.
- Critical evidence sources: GitHub Actions YAML, variable-name inventory with no values, environment names and deployment notes.
- Status: NOT VERIFIED from primary artifacts in this example. A real invocation must attach the files or authorize a read-only source inspection and record exact references.
- CHECKS THE SKILL WILL RUN
- Extract secrets.* and vars.* references with file and line context, including reusable workflows.
- Compare names against the user-provided inventory; never request or reveal the corresponding values.
- Check production/staging environment scope and case-sensitive spelling consistency.
- Flag competing names for the same logical secret and branch-specific deployment confusion.
- Provide a repair sequence, minimal dry-run checks and rollback plan with redacted diagnostics.
-
CORRECTION TO PROPOSE
Map one canonical variable name for Preview and update the workflow reference after owner review. Do not present this as implemented until the seller/developer actually applies the change and reviews the result. -
REPRODUCTION / ACCEPTANCE TEST
Trigger a safe workflow dry-run and check authentication status without printing the secret. Capture the before/after witness (paths, commands, timestamp, observed outcome), distinguish a script signal from a working end-to-end product, and do not invent a PASS. -
SCOPE LIMIT
Does not verify whether a secret value is correct or whether the remote platform has applied it.
Final handoff: a clear evidence-linked issue list, copy-ready proposed changes where appropriate, a prioritized checklist, and a statement of exactly which tests were and were not run.
Connects securely to your tools. The creator never sees your data.
About this skill
SecretMap — CI Variable Reference Audit
Find undefined, shadowed and inconsistent secret names in CI and deployment configuration without reading secret values.
What you receive
- A ready-to-install skill with a repeatable, evidence-first procedure.
- A source-to-claim discrepancy matrix, severity tags and specific corrective actions.
- A clearly separated verification checklist and unknowns register.
- A representative worked example; it is not passed off as a live customer run.
Example issue
preview.yml references secrets.CRON_SECRET while the supplied inventory contains PREVIEW_CRON_SECRET only.
Trust boundary
Does not verify whether a secret value is correct or whether the remote platform has applied it.
No paid API subscription is bundled. The agent can inspect materials supplied by the buyer in its supported environment. Access to private services is never presumed.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
Does not verify whether a secret value is correct or whether the remote platform has applied it.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 8 days ago
Nothing to install. It runs in your AI agent.
- Optional
Python 3
Python is only for the optional local read-only helper.
Permissions
File Scopes
No production changes or account access without owner authorization.