chameleon-trust

Validate chameleon profiles for secure Claude Code sessions.

9|3|Updated May 10, 2026
One-click install
npx skills add https://github.com/crisnahine/chameleon --skill chameleon-trust
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: chameleon-trust
Source: https://github.com/crisnahine/chameleon/tree/main/plugin/skills/chameleon-trust
Command: npx skills add https://github.com/crisnahine/chameleon --skill chameleon-trust

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes scripts (resource) components.

What problem does it solve?

The chameleon-trust skill ensures code safety and adherence to repository conventions by approving chameleon profiles for trust in Claude Code sessions.

Core Features & Use Cases

  • Profile Approval: Trusts committed .chameleon/profile.json files for safe usage in the Claude Code session.
  • Security Verification: Protects against insecure patterns, prompt-injection payloads, and subtly poisoned profiles.
  • Usage Confirmation: Asks for the repo root directory name or an 8-character prefix for trust confirmation.
  • Material-change Re-prompt: Trust re-verification is prompted only when necessary, avoiding unnecessary prompts.

Quick Start

Approve a committed profile by running the /chameleon-trust command with the appropriate repo root directory name.

Frequently Asked Questions about chameleon-trust

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code safety for a Claude Code session using chameleon profiles?β–Ό

Code safety in a Claude Code session is verified by validating the committed .chameleon/profile.json file against insecure patterns and prompt-injection payloads, ensuring secure code editing practices.

How do I approve a chameleon profile for repository trust in Claude Code?β–Ό

To approve a chameleon profile for repository trust, run the /chameleon-trust command and provide the repo root directory name or an 8-character prefix to confirm secure usage.

What insecure coding practices does chameleon profile validation prevent?β–Ό

Chameleon profile validation prevents insecure coding practices by detecting prompt-injection payloads, subtly poisoned profiles, and patterns that violate repository conventions before code analysis begins.

Does repository trust validation re-prompt for every code change in Claude Code?β–Ό

Repository trust validation does not re-prompt for every change; chameleon-trust only triggers trust re-verification when material changes to the profile occur, avoiding unnecessary prompts.

Do I need a specific file format to enforce coding conventions with chameleon-trust?β–Ό

Yes, convention enforcement requires a committed .chameleon/profile.json file located at the repository root to perform code analysis and safety checks within Claude Code.

When should I not use chameleon profile approval for code review?β–Ό

Chameleon profile approval is not applicable for code review when a repository does not use Claude Code or lacks a .chameleon/profile.json file for safety checks and convention enforcement.