skills/context-loader/SKILL.md
Load project context efficiently for Conductor workflows. Use when starting work on a track, implementing features, or needing project context without consuming excessive tokens.
npx skillsauth add pilotparpikhodjaev/conductor_cc context-loaderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Efficiently load and manage project context for Conductor's context-driven development workflow.
Use this skill when:
/conductor:implement workflowBefore scanning files, check for:
.claudeignore - Claude-specific ignores.gitignore - Standard git ignores# Check for ignore files
ls -la .claudeignore .gitignore 2>/dev/null
Use git for tracked files:
git ls-files --exclude-standard -co | head -100
For directory structure:
git ls-files --exclude-standard -co | xargs -n 1 dirname | sort -u
| Priority | File Type | Examples |
| -------- | --------- | ------------------------------------------------- |
| 1 | Manifests | package.json, Cargo.toml, pyproject.toml |
| 2 | Conductor | conductor/product.md, conductor/tech-stack.md |
| 3 | Track | conductor/tracks/<id>/spec.md, plan.md |
| 4 | Config | tsconfig.json, .env.example |
For files over 1MB:
1. Load CLAUDE.md (if exists)
2. Load conductor/product.md (project vision)
3. Load conductor/tech-stack.md (technical context)
4. Load current track spec.md (requirements)
5. Load current track plan.md (tasks)
After loading context, summarize:
## Project Context Loaded
**Product**: [one-line summary]
**Tech Stack**: [key technologies]
**Current Track**: [track name/id]
**Active Phase**: [current phase]
**Pending Tasks**: [count]
tools
Manage Conductor tracks, phases, and tasks. Use when working with track status, updating task markers, or navigating between tracks.
development
Apply language-specific style guide rules to your code. Use when writing or reviewing code to ensure consistency with best practices.
testing
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".
testing
Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).