Analyze agent-user interaction transcripts to identify context network maintenance needs and guidance improvements. Use after significant agent interactions or to improve context networks.
npx claudepluginhub joshuarweaver/cascade-content-creation-misc-1 --plugin jwynia-agent-skills-1This skill uses the workspace's default tool permissions.
Analyze agent-user interaction transcripts to identify context network maintenance needs and guidance improvements. Extract actionable insights for enhancing both network structure and agent instructions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Analyze agent-user interaction transcripts to identify context network maintenance needs and guidance improvements. Extract actionable insights for enhancing both network structure and agent instructions.
Learn from every interaction. Each transcript reveals gaps in context, navigation issues, and guidance problems that can be systematically fixed.
Look For:
Questions:
Output: Missing information nodes and relationship gaps
Look For:
Questions:
Output: Boundary violations and guidance improvements needed
Look For:
Questions:
Output: Navigation improvements and missing connections
Look For:
Questions:
Output: Abstraction adjustments and reorganization needs
Look For:
Questions:
Output: Missing relationships and documentation needs
Look For:
Questions:
Output: Guidance refinements and rule clarifications
Context Gathering
Baseline
Chronological Analysis
Critical Incidents
Pattern Recognition
Information Architecture
Guidance System
Prioritization
## Gap: [Name]
**Discovery Context:** [When/how revealed]
**Task Impact:** [How it affected completion]
**Information Type:** [Domain/Process/Relationship/Decision criteria]
**Recommended Action:** [Specific node or relationship to add]
**Priority:** [Critical/High/Medium/Low]
**Related Gaps:** [Connected gaps]
## Issue: [Name]
**Problem Pattern:** [What difficulty occurred]
**Information Sought:** [What agent wanted]
**Current Path:** [How agent actually found it]
**Optimal Path:** [How it should be discoverable]
**Recommended Improvement:** [Specific changes]
**Affected Tasks:** [What else would benefit]
## Guidance: [Mode/Rule Area]
**Expected Behavior:** [What guidance should produce]
**Actual Behavior:** [What agent did]
**Deviation Analysis:** [Why different]
**Guidance Clarity:** [Current clarity level]
**Recommended Changes:** [Specific modifications]
**Test Scenarios:** [How to validate]
| Pattern | Solution |
|---|---|
| Repeatedly seeks same info | Create hub document, improve linking |
| Confusion about file placement | Enhance boundary guidance with examples |
| Task context scattered | Create task-specific entry points |
| Decisions without consulting context | Strengthen "consult before action" guidance |
| Info not at right abstraction | Multi-layered nodes with progressive disclosure |
Phase 1: Critical Infrastructure
Phase 2: Navigation Enhancement
Phase 3: Guidance Refinement
Phase 4: Optimization
Pattern: Attributing interaction failures to agent capability rather than context gaps. "The agent should have known..." Why it fails: Agents operate from context. If context is incomplete, even capable agents fail. Blaming agents prevents systemic improvement. Fix: Assume context gaps first. Ask "what information would have prevented this?" before "why didn't the agent figure it out?"
Pattern: Believing context networks can capture everything. Adding more and more information hoping to prevent all failures. Why it fails: Context networks grow without bound. Navigation becomes impossible. Signal-to-noise ratio degrades. Maintenance becomes unsustainable. Fix: Focus on high-impact gaps. Prioritize what actually caused failures. Remove outdated information as aggressively as you add new.
Pattern: Fixing the specific issue without identifying the pattern. Adding a fact that was missing without asking why it was missing. Why it fails: Treats symptoms, not causes. The same class of gap will appear elsewhere. Whack-a-mole maintenance. Fix: Classify gaps by type. If the gap is "missing relationship documentation," the fix is improving relationship capture, not adding one relationship.
Pattern: Running retrospectives but never implementing changes. Analysis paralysis or action avoidance. Why it fails: Insight without action produces no improvement. Accumulating analysis without implementation wastes the analysis effort. Fix: Every retrospective must produce at least one actionable change. Schedule implementation before finishing retrospective.
Pattern: Adding more rules and restrictions after every failure. Context networks become constraint lists. Why it fails: Excessive guidance produces paralysis. Agents become afraid to act. Guidance conflicts emerge. Nobody reads the rules. Fix: Before adding guidance, consider removing it. Simplify before complexifying. Test if clearer boundaries achieve more than more rules.
Inbound:
Outbound:
Complementary: