Help us improve
Share bugs, ideas, or general feedback.
From code
Provides ClosedLoop environment paths (CLOSEDLOOP_WORKDIR, CLAUDE_PLUGIN_ROOT) for agents accessing run directories, plugin schemas, PRD files, and learnings.
npx claudepluginhub closedloop-ai/claude-plugins --plugin codeHow this skill is triggered — by the user, by Claude, or both
Slash command
/code:closedloop-envThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides access to ClosedLoop environment variables needed for file operations.
Knowledge base on Claude Code formats, patterns, and configurations for commands, agents, skills, hooks, memory, plugins, settings. Use for creating, improving, auditing components.
Lists Claude Code components: skills (personal/project/plugin via Python scan), env-vars, sessions, settings, tools. Invoke with /list <action>.
Guides capturing high-quality, generalizable learnings from ClosedLoop runs using decision tree, rejection criteria, and workflow to classify into CLAUDE.md or org-patterns.toon.
Share bugs, ideas, or general feedback.
This skill provides access to ClosedLoop environment variables needed for file operations.
Read the base environment file:
.closedloop-ai/env
The file contains KEY=VALUE pairs:
CLOSEDLOOP_WORKDIR - The run directory for this sessionCLAUDE_PLUGIN_ROOT - The plugin installation directoryCLOSEDLOOP_PRD_FILE - Path to the PRD fileCLOSEDLOOP_MAX_ITERATIONS - Maximum loop iterationsAfter reading the env file, construct paths like:
{CLAUDE_PLUGIN_ROOT}/schemas/plan-schema.json{CLOSEDLOOP_WORKDIR}/plan.jsonAlso read your agent-specific learnings file if it exists:
.closedloop-ai/learnings-{your-agent-name}
Where {your-agent-name} is your name: from your frontmatter in lowercase (e.g., plan-validator).
The learnings file contains an <organization-learnings> block with patterns from previous runs. These learnings capture what worked well and should be applied to improve your performance.
When learnings are present: