agentleFS
ibahgatibahgat/oh-my-iflow/skills/hooks/SKILL.md

hooks

Skill2 starsChanged 8 months agoMITView on GitHub

Operate omi's extension-native hook pipeline with deterministic triggers, safety gates, and efficiency budgets.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to keep long sessions stable by turning recurrent workflow signals into explicit hook actions.

    line 8
  2. Distinctive:

    Do not enable side-effect hooks in worker sessions unless user explicitly requests.

    line 26
  3. Distinctive:

    Keep non-critical hooks fail-open to avoid deadlocks.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Purpose

Use this skill to keep long sessions stable by turning recurrent workflow signals into explicit hook actions.

Trigger

  • User asks for hook setup, hook tuning, or hook debugging
  • Session has repeated blockers, context drift, or verify-loop churn
  • Team needs safer autonomous operation in delegated/worker turns

Workflow

  1. Identify active native events and needed derived signals.
  2. Assign each trigger to one execution lane (P0-safety, P1-quality, P2-optimization).
  3. Enforce deterministic order, idempotency keys, debounce, and timeout budgets.
  4. Enforce team-safety policy for worker/delegated sessions.
  5. Recommend validation (/omi:hooks-validate) and dry-run (/omi:hooks-test) before high-autonomy loops.

Guardrails

  • Do not enable side-effect hooks in worker sessions unless user explicitly requests.
  • Keep non-critical hooks fail-open to avoid deadlocks.
  • Escalate when hook failures are safety-critical or repeatedly blocking progress.

Output Template

## Hook Plan
- profile:
- enabled events:
- derived signals:

## Lane Assignment
| Lane | Triggers | Purpose | Budget |
| --- | --- | --- | --- |

## Safety Policy
- ...

## Next Commands
1. /omi:hooks-validate
2. /omi:hooks-test

Download now (ZIP)

  • Other versions21 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 21

    1. parcadei/Continuous-Claude★ 3.9ksame name
    2. parcadei/Continuous-Claude-v2★ 3.9ksame name
    3. parcadei/Continuous-Claude-v3★ 3.9ksame name
    4. duncan-buildroom/freeskills★ 64same name
    5. nimadorostkar/Claude-Skills-collection★ 29same name
    6. duncan-buildroom/profit-room-skills★ 18same name
    7. coopersimson96/ai-content-system★ 17same name
    8. AI-Answer/ContentRepurposeSystem★ 15same name
    9. issue-orchestrator/issue-orchestrator★ 9same name
    10. Samin12/skills★ 8same name

    11 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use yt-titles, outlines and 1 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • Samin12Skill

      yt-titles

      Generate high-performing YouTube title ideas based on the user's video content description, cross-referenced with your recent top-performing videos. Use this skill whenever the user wants YouTube title suggestions, asks "what should I title this video", "give me title ideas", "title options for my video about...", "help me name this video", brainstorming video titles, or any request involving YouTube title generation or optimization. Also trigger when the user mentions titling, naming, or headlining a YouTube video even casually.

      Also in 3 projects that use this

    • Clay-HHKSkill

      outlines

      Guarantee valid JSON/XML/code structure during generation, use Pydantic models for type-safe outputs, support local models (Transformers, vLLM), and maximize inference speed with Outlines - dottxt.ai's structured generation library

      Also in 3 projects that use this

    • BlockSkill

      frontend-design

      Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

      Also in 3 projects that use this

  • In this repository24 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.