Menu

Individual skill

generalize

0upvotes

Generalize a concrete fix, example, correction, or recurring failure into evidence-backed broader solutions and durable prevention. Use when explicitly asked to broaden, systematize, or extract transferable lessons.

generalize/SKILL.md

Read pinned source

Source commit 1acf58f08cca24b764a4352a6c30fed1f7fb9fb6

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
197
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Generalize

Surface meaningful improvements at multiple levels and recommend the option that best fits the user's intent and impact-versus-effort tradeoff.

1. Establish the user's actual goal, authorized scope, observed examples, and underlying failure mechanism.
2. Inspect the current conversation, established workflow, and relevant code, data, tests, or logs. Reuse existing parsers, contracts, and resume mechanisms before proposing another path. Search available agent session history only when past decisions or recurrence could change the conclusion; target exact repository names, errors, or phrases, bound the search, and avoid secrets or unrelated private content.
3. Find sibling cases and counterexamples. Generalize only the verified cause; do not turn a local defect into new policy, requirements, or architecture without supporting evidence. Distinguish a one-off symptom, repeated pattern, missing invariant, unreliable input, and architectural constraint; quantify affected cases when practical.
4. Offer only useful levels of intervention:
   - Fix the immediate instance.
   - Repair other cases sharing the same verified cause.
   - Correct the shared data, contract, abstraction, or workflow.
   - Add a test, guardrail, monitoring, or safe automation.
   - Capture a reusable process, skill, or architectural improvement.
5. Compare expected impact, confidence, effort, risk, reversibility, and dependencies. Recommend based on the user's overall intent; favor simplicity when outcomes are comparable, but surface higher-impact options that become worthwhile with broader scope or authorization. Mark speculation and unresolved cases explicitly.
Back to top