Skip to content
Back to skills

Openloomi Hooks

ASecurity

OpenLoomi × Claude Code hooks installer. Use when the user wants Claude Code's lifecycle (SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, Stop, SubagentStart, SubagentStop, Notification) to mirror onto the Loomi Pet, or wants to auto-archive every Stop into OpenLoomi memory. Triggers: install hooks, /openloomi:hooks, hooks install, hooks uninstall, hooks status, mirror claude on pet, auto-archive stop.

  • 1,036 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added August 31, 2026
ai-agentsbashnode

Works with

  • claude code

Security analysis

A100/100

Scanned August 31, 2026

npx -y skills add melandlabs/openloomi --skill openloomi-hooks --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Openloomi Hooks?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Openloomi Hooks
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/melandlabs-openloomi-hooks/badge)](https://www.skillsdirectory.com/skills/melandlabs-openloomi-hooks)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: openloomi-hooks
description: "OpenLoomi × Claude Code hooks installer. Use when the user wants Claude Code's lifecycle (SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, Stop, SubagentStart, SubagentStop, Notification) to mirror onto the Loomi Pet, or wants to auto-archive every Stop into OpenLoomi memory. Triggers: install hooks, /openloomi:hooks, hooks install, hooks uninstall, hooks status, mirror claude on pet, auto-archive stop."
allowed-tools: Bash(node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs *)
---

# OpenLoomi Hooks Sub-skill

The plugin ships a hook bundle in `hooks/hooks.json` but **never installs it
automatically**. Users must explicitly run one of:

- `/openloomi:hooks install` — merge the bundle into `~/.claude/settings.json`
- `/openloomi:hooks uninstall` — strip only the plugin's block (other
  plugins' hooks are preserved)
- `/openloomi:hooks status` — report whether the bundle is currently active

Under the hood this calls:

```bash
node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs install-hooks
node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs uninstall-hooks
node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs hooks-status
```

## Safety guarantees

- `install-hooks` is **merge-no-overwrite**: only adds the plugin's block
  under `hooks.__openloomi_claude_plugin_hooks__`. Existing hooks for
  other plugins are not touched.
- `uninstall-hooks` removes only the plugin-marked block; rerunning it
  after the first time reports `removed: false`, never deletes anything
  else's hooks.
- The merge is atomic (`writeFile` to a temp file, then `rename`).
- The Stop hook **always exits 0** — archive failures are reported as
  JSON `{continue: true, _openloomi: {archive: "skipped", reason: ...}}`
  so they can never block Claude Code's response stream.

## Suggested user prompt

> This plugin can mirror Claude Code's lifecycle onto your Loomi Pet. To
> enable this, run `/openloomi:hooks install`. To disable, run
> `/openloomi:hooks uninstall`. The plugin never modifies your
> `~/.claude/settings.json` without explicit consent.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.