canopy-intelligence

Pulls workspace context and persists durable project knowledge via Canopy MCP intelligence tools.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/UniverLab/univerlab --skill canopy-intelligence-univerlab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canopy-intelligence
Source: https://github.com/UniverLab/univerlab/tree/main/public/.well-known/agent-skills/canopy-intelligence
Command: npx skills add https://github.com/UniverLab/univerlab --skill canopy-intelligence-univerlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents lose everything they learned when a session ends, forcing every future session to re-derive project conventions, constraints, and architectural decisions from scratch. This Skill teaches an agent to use the Canopy Project Intelligence Layer (PIL) so knowledge outlives individual sessions. ## Core Features & Use Cases - Session-start context pull: Call get_tools(scope="session_start") to receive the workspace brief, and intelligence_get_context(scope="full") for deep architecture work or onboarding. - Durable knowledge persistence: Register facts (conventions, constraints, configuration truths) and patterns (recurring code structures, workflow rules, architectural decisions) with intelligence_upsert so future sessions inherit them. - Session closure protocol: Call get_tools(scope="close_session") to upsert a session summary and report workspace status before ending. - Use Case: While exploring a Rust codebase, you discover that all DB tables use snake_case with an _at suffix. You upsert it as a fact immediately, and the next agent session starts already knowing the convention. ## Quick Start Ask the agent to pull the Canopy session-start context and upsert any durable conventions it discovers during this session.

Frequently Asked Questions about canopy-intelligence

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

FAQPage Schema
How do I persist project knowledge across agent sessions?

Use intelligence_upsert with kind set to fact or pattern, passing a title and body. The project_hash is auto-detected from your session workdir, so future sessions on the same project inherit the knowledge automatically.

When should I call intelligence_get_context versus get_tools?

Call get_tools with scope session_start at the beginning of every session to get the workspace brief. Use intelligence_get_context with scope full only for deep architecture work or onboarding that needs complete project context.

Does canopy-intelligence work without the Canopy MCP server?

No. This skill is inert without the Canopy MCP tools (get_tools, intelligence_*) present in the session. It declares requires = "canopy" and should not be installed on hosts that never run Canopy.

What is the difference between upserting a fact and a pattern?

Facts cover conventions, constraints, naming rules, and configuration truths, such as a default daemon port. Patterns cover recurring code structures, workflow rules, architectural decisions, and testing conventions observed across the codebase.

What should I do when the intelligence layer contradicts the code?

Treat the intelligence layer as stale and update it first with intelligence_upsert, then continue your work. Stale intelligence confidently misleads every future agent session.