agentsclimarketplace

Omega3 start

Skill mohamed-essam/omega3-template/skills/omega3-start

Orient any session to the omega3 knowledge hub — loads a lazy summary (README gist, systems/ + knowledge/ indexes, the current repo's system note) and surfaces pending insight proposals. Fires automatically via the SessionStart hook; invoke manually to re-orient.From its SKILL.md

Install
npx -y skills add mohamed-essam/omega3-template --skill omega3-start

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

2 things to look at

  • 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 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.

SKILL.md

2.3 KB, 510 tokens by cl100k_base, as published. Nobody here has run it

omega3-start

omega3 (__OMEGA3_HOME__) is your central, durable knowledge hub across all the repos you work in. This skill makes the current agent aware of it cheaply — it does NOT read every note, only the indexes and the note for the current repo.

When this runs

  • Automatically at session start, via the SessionStart hook (see ~/.claude/settings.json), which runs .omega/orient.sh.
  • Manually, when you want to re-orient or the hook didn't fire.

Do this

  1. Run the orientation script and read its output:
    bash __OMEGA3_HOME__/.omega/orient.sh "$PWD"
    
    It prints: the hub location + conventions, the systems/ and knowledge/ indexes, the current repo's systems/<repo>.md (if any), and counts of pending proposals / inbox items.
  2. Keep that context in mind for the rest of the session. Do not now read every note — pull individual notes on demand by following [[wikilinks]] from the indexes.
  3. For deep/relational questions about any system, prefer the prebuilt graph if you use the optional graphify layer: if __OMEGA3_HOME__/graphify-out/graph.json exists, run graphify query "<question>" from the omega3 dir. Otherwise read the relevant INDEX.md and follow links.
  4. If the script reports pending insight proposals, mention it to the user once and suggest /omega3-review.

End-of-session capture (standing directive for the whole session)

Hold this for the entire session, not just at start: the moment the session looks ~complete — the task/work is done, or the user says thanks / done / bye / "that's all", or otherwise signals wrapping up — proactively remind the user to run /omega3-end before the session ends. Offer it; don't wait to be asked. Never let a work session close uncaptured (that's how durable knowledge + promotion evidence is lost). If the session did no substantive work, it's fine to skip the reminder.

Guardrails

  • Read-only. This skill never writes.
  • If omega3 isn't present on this machine, the script no-ops — do nothing further.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,645. 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.