Adaptive Skill Stack

This skill is coherent with its description (it keeps a registry and writes new capability entries and resources to disk). The main risk is persistence: after each task it will append to its registry and may create new scripts/templates inside the skill folder, effectively evolving its behavior across runs. Before installing or enabling autonomous invocation, consider: - Run the skill in a sandbox or restricted environment where the skill directory is isolated and has no access to sensitive files or networked mounts. - Disable autonomous invocation or require explicit user confirmation before the agent performs file writes or executes any newly created scripts. - Audit and review any files created under references/, scripts/, and assets/ after each run; especially inspect new scripts (*.py) and templates before allowing them to execute. - If you need stronger guarantees, make the capability-registry and protocols files read-only by default and require an explicit manual 'commit' step to accept suggested changes. Confidence is medium because the skill's behavior is internally consistent, but the persistence/self-modifying pattern raises non-negligible operational risk that depends on runtime governance (sandboxing, manual review, agent invocation policy).