alfredolopez80/context-engineer
.claude/skills/context-engineer/SKILL.md
Determines WHAT context an agent needs and packages it optimally. Actions: analyze (identify needed context), load (assemble from sources), prune (trim to token budget), inject (write to .claude/context-payload.md). Use when: (1) before spawning teammates, (2) context window is limited, (3) multi-source context assembly. Triggers: /context-engineer, 'prepare context', 'package context', 'context for agent'.
$ install --global
skillsauthnpx skillsauth add alfredolopez80/multi-agent-ralph-loop context-engineerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 6:06 PM18.2s1 file scanned
SKILL.md
- # VERSION:
- 3.0.0
- name:
- context-engineer
- description:
- Determines WHAT context an agent needs and packages it optimally. Actions: analyze (identify needed context), load (assemble from sources), prune (trim to token budget), inject (write to .claude/context-payload.md). Use when: (1) before spawning teammates, (2) context window is limited, (3) multi-source context assembly. Triggers: /context-engineer, 'prepare context', 'package context', 'context for agent'.
- argument-hint:
- <task description>
- user-invocable:
- true
Context Engineer v3.0
Determine what context an agent needs and package it within token budget.
Actions
/context-engineer analyze <task>
Identify what context sources are relevant:
- Parse task description for domain keywords
- Check for DESIGN.md (frontend tasks)
- Check for .spec.md files (spec-driven tasks)
- Check memory sources (vault, handoffs, ledgers)
- Check codebase files (Glob/Grep for related code)
- Output: ranked list of context sources with estimated tokens
/context-engineer load <task>
Assemble context from identified sources:
- Run
analyzeif not already done - Read each source, extract relevant sections
- Prioritize by relevance score
- Output: assembled context block
/context-engineer prune <budget>
Trim assembled context to fit token budget:
- Default budget: 8000 tokens
- Remove low-relevance sections first
- Summarize long sections instead of including full text
- Preserve: interfaces, invariants, design tokens (high signal)
- Output: pruned context within budget
/context-engineer inject
Write packaged context to .claude/context-payload.md:
- Write pruned context to file
- The
ralph-subagent-start.shhook reads this file and injects into teammate prompt - File is gitignored (per Item 0a)
Context Sources (Priority Order)
| Source | When Relevant | Token Cost | |---|---|---| | .spec.md | Task has a spec | ~500-2000 | | DESIGN.md | Frontend task | ~1000-3000 | | Related code files | Always | ~500-5000 | | Memory (vault) | Prior work exists | ~200-500 | | Handoffs | Cross-session | ~300-800 | | Vault (future) | Curated knowledge | ~200-1000 |
Integration
- Orchestrator Step 5 (DELEGATE): invoke before spawning teammate
- ralph-subagent-start.sh: reads
.claude/context-payload.mdif exists - Token budget: default 8000, adjustable per task complexity
Anti-Rationalization
| Excuse | Rebuttal | |---|---| | "The agent has enough context from the prompt" | Agents lose 40% accuracy without structured context. Package it. | | "Context engineering is overhead" | 5 seconds of packaging saves 5 minutes of wrong output. | | "I'll just include everything" | Token flooding degrades quality. Prune to signal. |
Related Skills
alfredolopez80/vault
development
VerifiedTrustedCommunity
Living knowledge base management. Actions: search (query vault), save (store learning), index (update indices), compile (raw->wiki->rules graduation), init (create vault structure). Follows Karpathy pipeline: ingest->compile->query. Use when: (1) searching accumulated knowledge, (2) saving learnings, (3) compiling raw notes into wiki, (4) initializing a new vault. Triggers: /vault, 'vault search', 'knowledge base', 'save learning'.
121SKILL.mdUpdated Apr 15, 2026
alfredolopez80/spec
testing
VerifiedTrustedCommunity
Produce a verifiable technical specification before coding. 6 mandatory sections: Interfaces, Behaviors, Invariants (from Aristotle Phase 2), File Plan, Test Plan, Exit Criteria (executable bash commands + expected results). Use when: (1) before implementing features with complexity > 4, (2) as Step 1.5 in orchestrator workflow, (3) when requirements need formalization. Triggers: /spec, 'create spec', 'write specification', 'technical spec'.
121SKILL.mdUpdated Apr 15, 2026
alfredolopez80/ship
testing
VerifiedTrustedCommunity
Pre-launch shipping checklist orchestrating /gates, /security, /browser-test, /perf. Ensures nothing ships without passing all quality checks. Use when: (1) before deploying, (2) before merging to main, (3) before release. Triggers: /ship, 'ship it', 'ready to deploy', 'pre-launch check'.
121SKILL.mdUpdated Apr 15, 2026
alfredolopez80/perf
development
VerifiedTrustedCommunity
Performance optimization skill. Core Web Vitals via Lighthouse, bundle size analysis, metrics tracking over time. Use when: (1) optimizing frontend performance, (2) analyzing bundle size, (3) tracking metrics regression. Triggers: /perf, 'performance audit', 'core web vitals', 'bundle size'.
121SKILL.mdUpdated Apr 15, 2026