Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Deep telemetry and observability for Claude Code. Captures tool calls, plugin usage, skill invocations, errors, performance metrics, and provides rich querying, analysis, and insights.
Show slash command usage, success rates, and completion times
Compare two sessions or time periods to detect changes
Manage the cc-telemetry background daemon (start/stop/status/restart)
Launch the cc-telemetry web dashboard for visual exploration of sessions, tool calls, errors, and token usage
Show error log with full context including stack traces and tool chains
Query Claude Code telemetry. Shows real-time tool call history, session stats, error rates, hook events, and timing data from the cc-telemetry daemon watching ~/.claude/projects/ transcripts. Use to debug plugin issues, understand usage patterns, or audit what tools Claude called.
Use when the user reports a problem with a specific Claude Code session, needs to diagnose why something went wrong, wants to understand errors in detail, or asks "what happened in my last session". Trigger on phrases like "debug my session", "why did that fail", "what went wrong", "replay my session", or when investigating specific errors.
Use when the user wants to improve their Claude Code usage efficiency, reduce errors, speed up workflows, or asks "how can I be more productive", "optimize my usage", "what am I doing wrong", or wants suggestions to work more effectively.
Matches all tools
Hooks run on every tool call, not just specific ones
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Runs pre-commands
Contains inline bash commands via ! syntax
Runs pre-commands
Contains inline bash commands via ! syntax
Share bugs, ideas, or general feedback.
Opinionated meta skills & plugin framework for deterministic results with Claude Code.
Lore bundles battle-tested skills, commands, agents, and workflows into a single Claude Code plugin. It provides structured approaches to common development tasks — from TDD and debugging to code review, feature research, and security scanning — so Claude follows repeatable, high-quality processes instead of improvising.
curl -fsSL https://raw.githubusercontent.com/LayerDynamics/lore/main/install.sh | bash
The installer clones the repo into ~/.claude/plugins/_src/lore, symlinks the plugin into ~/.claude/plugins/lore, optionally sets up extensions (browserx, trellio, cc-telemetry, findlazy, mcp-trigger-gateway, scratchpad), and offers to launch Claude Code with a guided tour.
Verify the installation:
# In a Claude Code session:
/lore:list
Once installed, Lore's skills and commands are available in any Claude Code session.
List everything available:
/lore:list
Run a security scan on your project:
/security-check:scan
Start a TDD workflow:
Use the test-driven-development skill to implement [your feature]
Plan a multi-step feature:
/planning-ext:plan
Deep-dive into unfamiliar code:
/code-intel:investigate how does authentication work in this project?
Research before building:
/research:research how to add WebSocket support --depth deep
Review code without git:
/local:local-code-review src/
Audit dependencies and configs:
/security-check:audit
Skills are the core abstraction — structured markdown workflows (each a SKILL.md) that guide Claude through complex tasks deterministically. Skills are invoked by name in conversation or triggered automatically based on context.
| Skill | What It Does | When to Use |
|---|---|---|
brainstorming | Collaborative dialogue to explore intent, requirements, and design before implementation. Proposes 2-3 approaches with trade-offs, gets approval, then writes a design doc. | Before any creative or feature work — always brainstorm first |
lifecycle-phases | Enforces a Clarify → Plan → Execute → Review lifecycle with wave-based parallel execution for each phase. | Managing project execution through structured phases |
rarv-cycle | Core execution loop: Reason → Act → Reflect → Verify. Every autonomous action follows this cycle — no step is optional. | Any autonomous or semi-autonomous work |
staying-on-request | Enforces task boundaries — do exactly what was asked, nothing more. Surfaces adjacent issues as TODOs without fixing them. | When you discover adjacent issues or feel tempted to refactor |
context-engineering | Manages agent context windows, preserves state across sessions, coordinates information flow between agents. | When context is getting large or coordinating multiple agents |
subagent-development | Executes implementation plans by dispatching a fresh subagent per task with two-stage review (spec compliance + code quality) after each. | Executing implementation plans with independent tasks |
writing-plans | Guided discovery followed by a structured implementation plan. Reads project context, asks about inclusions and dev practices, writes a bite-sized plan to docs/plans/. | When you have a spec or requirements for a multi-step task |
| Skill | What It Does | When to Use |
|---|---|---|
debug | General debugging with root cause investigation. No fixes without understanding the cause first. | Encountering bugs, test failures, or unexpected behavior |
systematic-debugging | Four-phase investigation methodology: reproduce → isolate → identify root cause → fix. Random fixes waste time. | Any bug or test failure — must complete all phases before proposing fixes |
deep-investigation | Traces execution paths, follows call chains, maps service integrations, reads tests, surfaces exact file:line references. | Tracing how something works, investigating execution paths, preparing for code review |
reading-unfamiliar-code | Efficiently orients in unfamiliar projects. Starts with entry points and project-level docs before reading source files. | New to a project, need to understand architecture before making changes |
outline-understanding-user-request | Analyzes actual code (not docs) to understand ambiguous requests. Identifies affected systems and formulates clarifying questions. | Ambiguous requests that would drain context to understand |
Native BrowserX browser automation — SQL-like queries, screenshots, scraping, form filling, proxy control. Automatically preferred over WebFetch/WebSearch for all web tasks.
Static analysis tool for detecting lazy-loaded code patterns, dead code, and unused imports across TypeScript and Python codebases.
Trellio task management commands and MCP integration.
MCP trigger gateway that fires events to invoke actions across MCP servers, HTTP endpoints, and shell commands.
npx claudepluginhub layerdynamics/lore --plugin cc-telemetryVerification-first engineering toolkit for Claude Code. 15 skills across a 5-phase spine (Investigate → Design → Implement → Verify → Ship), 8 specialist agents, an interactive setup wizard. Every skill has rationalizations + evidence requirements. Built for senior ICs and tech leads.
Core skills: ecosystem guide, skill creator, research patterns, session reflection, and plugin development. Includes UserPromptSubmit hook for forced skill evaluation.
Systematic debugging and root cause analysis framework - four-phase investigation process ensuring understanding before fixes
Custom commands, skills, agents, rules, hooks, and output styles for Claude Code - session continuity and modern CLI tooling for real-world development workflows
Claude Essentials - Unified development plugin with 9 commands, 24 skills, and 4 specialized agents
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques