session-intelligence-harvester

Encode session corrections and patterns into RII components with commits.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/ayeshakhalid192007-dev/humanoid-ai-studio --skill session-intelligence-harvester-ayeshakhalid192007-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-intelligence-harvester
Source: https://github.com/ayeshakhalid192007-dev/humanoid-ai-studio/tree/main/.claude/skills/session-intelligence-harvester
Command: npx skills add https://github.com/ayeshakhalid192007-dev/humanoid-ai-studio --skill session-intelligence-harvester-ayeshakhalid192007-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After productive sessions, teams struggle to convert corrections, discoveries, and recurring patterns into durable knowledge. This skill automates the encoding of learnings into Reusable Intelligence Infrastructure (RII) components, preventing drift and repeated mistakes.

Core Features & Use Cases

  • Parses session outcomes to extract corrections, patterns, and learning classifications.
  • Routes learnings to the appropriate RII components (CLAUDE.md, Constitution, chapter-planner, etc.) for timely integration.
  • Applies changes across multiple target files and commits them, ensuring end-to-end capture.

Quick Start

Harvest learnings from your latest session and encode them into the RII by updating the relevant files and making a commit.

Frequently Asked Questions about session-intelligence-harvester

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

FAQPage Schema
How do I convert session learnings into permanent organizational intelligence?

Encoding session learnings into permanent organizational intelligence involves parsing productive session outcomes to extract corrections, detected drift, and new patterns, then routing them to RII components like CLAUDE.md and Constitution files for durable persistence.

What's the best way to prevent knowledge drift after correcting mistakes during a Claude workflow?

Preventing knowledge drift after a Claude workflow requires harvesting corrections and new patterns from the session and encoding them across multiple RII target files, committing the changes to ensure end-to-end traceability and prevent repeated mistakes.

When do I need to harvest session outcomes into my knowledge-management infrastructure?

Harvesting session outcomes is needed after productive sessions where corrections were made, drift was detected, or new patterns emerged, ensuring these discoveries are classified and formally integrated into your organizational knowledge infrastructure.

How to apply cross-file changes and commit traceability for session analysis updates?

Applying cross-file changes for session analysis updates involves routing extracted learnings to the appropriate RII components and related skill files, applying the modifications across all targets, and making a commit to establish formal traceability.

Does this session harvesting approach require any specific dependencies or components?

This session harvesting approach requires no external dependencies or components, operating independently to parse session outcomes, classify learnings, and route updates to existing RII files like CLAUDE.md for immediate integration.

Can I use session harvesting for change management across multiple target files?

Session harvesting supports change management by applying extracted corrections and patterns across multiple target files simultaneously, satisfying formal update workflows and ensuring all related RII components reflect the new organizational learnings.