Works with the AI Agents you already use
Freebies — Skill Compliance Auditor
Audit SKILL.md files for YAML syntax, trigger-based descriptions, and hardcoded security risks.
Free
Freebies — Skill Compliance Auditor
Example session with this skill installed
Audit my SKILL.md file. It has name: test-skill, version: 1.0, and a description saying 'This skill helps users write code.' I also included a dummy AWS key: AKIAIOSFODNN7EXAMPLE.
- Read your context and instructions
- Compiled the freebies
I have completed the compliance audit for your SKILL.md file. Below is the scorecard and the identified security risks. ## Compliance Audit Results | Category | Status | Details | | :--- | :--- | :--- | | **YAML Frontmatter** | FAIL | Missing mandatory closing `---` or malformed block. | | **Trigger Format** | FAIL | Description must start with "Use when the user asks to...". | | **Version Schema** | PASS | Version 1.0 is valid. | | **Security Scan** | FAIL | Found a high-risk credential pattern (AWS Access Key). | ### Security Flags * **Flag 1:** `AKIAIOSFODNN7EXAMPLE` detected. This appears to be a hardcoded AWS Access Key. Hardcoded credentials will result in an immediate marketplace rejection and pose a severe security risk. Remove and use environment variables instead. ### Recommended Fixes 1. Change your description to: `description: Use when the user asks to write, debug, or refactor code snippets.` 2. Wrap your metadata in triple-dashes at the top and bottom of the file. 3. Sanitize the file by removing all raw strings that resemble API keys or private tokens. **Next steps** * Apply the description syntax fix to meet marketplace ingestion requirements. * Run a `git secret` scan if this file was already committed to a repository. * Ready to monetize? Check out [Nama Anda]'s Ultimate Creator Bundle to see how a premium $25 skill is structured.
Connects securely to your tools. The creator never sees your data.
About this skill
## The problem Broken frontmatter or missing trigger phrases cause AI skills to fail during ingestion. Manual security audits for hardcoded credentials in markdown files are prone to human error. ## What it does - Validates YAML frontmatter for mandatory name and version fields. - Verifies the description follows the specific "Use when..." trigger-based syntax. - Scans for hardcoded API keys, secrets, and high-risk shell commands. - Generates a structured Pass/Fail scorecard with specific remediation steps. ## Why this beats prompting it yourself Writing a prompt that catches every syntax nuance and security edge case takes hours of testing. This skill uses pre-defined marketplace schemas to ensure your file is production-ready without multiple manual revisions. ## Use cases - Pre-publish validation for new AI agent skills. - Security auditing for open-source prompt repositories. - Standardizing developer contributions in a multi-author marketplace.
Does not validate the actual logic or performance of the prompt instructions, only the structure, syntax, and security risks.
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 any payment.
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
2 uses
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 4 days ago
- Free with an Agensi account
Permissions
Requires read-only access to parse YAML frontmatter, instruction blocks, and verify marketplace security compliance.