agentsclimarketplace

Cross product learner

Skill hamza-ali-shahjahan/hamzaish/_archive/v0/agents/portfolio/cross-product-learner

Your Claude Code setup that builds, launches, and learns — across the whole product lifecycle. Point Claude Code at this and it runs your whole startup factory — and gets smarter every session. Works with Cursor, Codex & Windsurf too.

Install
npx -y skills add hamza-ali-shahjahan/hamzaish --skill cross-product-learner

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Identify patterns across products — what's working that should propagate, what's failing in similar ways, what knowledge should become MEMORY.md entries.

SKILL.md

2.2 KB, as published. Nobody here has run it

Cross-Product Learner

When you activate

  • Weekly review (Sunday)
  • After a product crosses a milestone (PMF, $1K MRR, $10K MRR, big retention shift)
  • User asks: "what patterns am I seeing across products?", "what's working that I should reuse?"

What you produce

Saved to brain/decision-log/learnings-YYYY-MM-DD.md and updates to MEMORY.md:

## Cross-Product Learnings — <week of>

### Patterns that should propagate
1. **<pattern>** — first seen in <product>, observed again in <product>. Action: extract to <skill / template / knowledge-base file>.
2. ...

### Patterns that are failing repeatedly
1. **<anti-pattern>** — observed in <products>. Reason it keeps happening: <root cause>. Mitigation: <change>.

### New entries proposed for MEMORY.md
- [<title>](<file>) — <one-line hook>

### New entries proposed for knowledge-base/
- knowledge-base/<stage>/<filename>.md — covering <topic>

### Templates that need updating
- templates/<file> — change: <what>

### Skills that need updating
- skills/<name>/SKILL.md — change: <what>

Protocol

  1. Read all products' recent decisions/ entries from the past week.
  2. Read the weekly review (if it exists).
  3. Look for:
    • The same problem solved twice → should be a template or skill
    • The same mistake made twice → should be a knowledge-base entry or operating principle
    • A novel approach that worked → should be a memory entry + maybe a skill update
    • A persistent failure mode → root-cause it, mitigate at the factory level
  4. Propose specific writes: which file, what content (summary).
  5. Confirm with user before writing new memory entries — memory bloat is worse than missing entries.

Sources

  • All products' decisions/ folders
  • brain/decision-log/
  • MEMORY.md

What you don't do

  • Don't write memory for one-off events. Memory is for things that recur.
  • Don't duplicate knowledge-base content in MEMORY — link to it.
  • Don't create skills for things that happen once. Skills are for repeated patterns.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.