10x-lesson

Appends recurring engineering rules to a lessons.md register for future reviews.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/michaail/hybrid-logs-analyzer --skill 10x-lesson-michaail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-lesson
Source: https://github.com/michaail/hybrid-logs-analyzer/tree/main/.cursor/skills/10x-lesson
Command: npx skills add https://github.com/michaail/hybrid-logs-analyzer --skill 10x-lesson-michaail

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Recurring bugs and design pitfalls get fixed once but forgotten, so the same class of mistake resurfaces in later framing, planning, and implementation work. This Skill captures those recurring rules into a persistent, append-only lessons register that future workflow runs re-read as priors. ## Core Features & Use Cases - Structured four-field interview: Collects Context, Problem, Rule, and Applies-to fields from the user so every lesson entry follows a canonical, scannable format. - Append-only register with self-bootstrap: Creates context/foundation/lessons.md with a canonical header on first use and appends new H2 entries without reordering or editing existing ones. - Use Case: While implementing a feature, you notice feature flags keep shipping without kill dates. Invoke the skill, answer the four prompts, and the rule is recorded so future plan and review passes weigh it automatically. ## Quick Start Ask the assistant to record a recurring rule as a lesson, for example: capture a lesson that feature flags should always have a kill date.

Frequently Asked Questions about 10x-lesson

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

FAQPage Schema
How do I capture a recurring engineering rule for future code reviews?

Invoke the skill with an optional freeform description of the rule, then answer four prompts covering Context, Problem, Rule, and Applies-to. The skill renders the entry for confirmation and appends it to context/foundation/lessons.md.

What is the difference between a lesson and a one-off bug fix?

A lesson is a recurring rule that would have changed framing or fixes on past work and will keep coming up. A single-incident write-up does not meet the bar and should not be captured through this skill.

Can I edit or delete existing lessons in lessons.md?

No, the register is append-only by design. The skill never edits, reorders, or deduplicates existing entries; if a rule needs revision, you open the file and edit it directly.

What happens if lessons.md does not exist yet?

The skill self-bootstraps the file with a canonical five-line header and then appends the new entry. You do not need to run any initialization step first.

When should I not use this lesson-capture approach?

Avoid it for one-off incidents, batching multiple lessons in one invocation, or pre-filling fields on behalf of the user. Each invocation captures exactly one user-written rule.