eld-sense-activation

Construct an optimized active_context YAML with goal, constraints, references, and expected_output.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/CAPHTECH/claude-marketplace --skill eld-sense-activation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eld-sense-activation
Source: https://github.com/CAPHTECH/claude-marketplace/tree/main/caphtech-plugin/skills/eld-sense-activation
Command: npx skills add https://github.com/CAPHTECH/claude-marketplace --skill eld-sense-activation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Builds an active context pool focused on the objective and constraints of the current task.

Core Features & Use Cases

  • Goal refinement for the active context
  • Boundary and constraints extraction
  • Reference selection to tailor the context

Quick Start

Provide a goal and constraints for the task, and this Skill will assemble a concise active context block.

Frequently Asked Questions about eld-sense-activation

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

FAQPage Schema
How do I structure context to drive precise task execution?

Active context activation constructs a focused YAML block containing goal, constraints, references, context, and expected output. This structured approach ensures task-specific information is organized and budgeted—goals up to 3 lines, constraints up to 5 items, references up to 3 files—so execution remains aligned with objectives and dependencies are explicit from the start.

When should I activate a new task context instead of reusing existing context?

Activate new task context when starting fresh tasks, requesting code generation, solving complex problems, or issuing context-summarization directives. New activation prevents scope creep, surfaces hidden constraints, and ensures dependencies are re-evaluated for the specific objective rather than carrying forward assumptions from prior work.

What's the difference between planning scope and defining constraints in context?

Scope defines what the task covers; constraints define what limits it. Planning extracts the goal (up to 3 lines); constraints collection (up to 5 items) captures budget, platform, technical debt, and dependency restrictions. Together they form the boundary that prevents task drift and ensures reproducible, focused execution.

How do I select the right references to include in active context?

Reference selection limits your active context to up to 3 files that directly inform task execution. Choose references that encode existing decisions, patterns, or dependencies relevant to the current goal. This compression keeps context lean while preserving institutional knowledge needed to maintain consistency and avoid redundant work.

Can I use context activation for ongoing work or only for new tasks?

Context activation works for both new tasks and ongoing work requiring re-focus. Use it when complexity grows, priorities shift, or you need to organize and summarize accumulated context. The compile workflow supports editing and compression, so you can refresh active context mid-project without starting over.

What happens if my task exceeds the context budget constraints?

Exceeding budget signals scope creep or missing decomposition. Compress goals by narrowing focus, prioritize top constraints and drop lower-impact ones, or reduce references to essential files only. If compression fails, the task may need to split into multiple focused tasks with separate active contexts rather than force-fit into one.