openloomi-handoff
GitHub通过OpenLoomi桥接脚本,将Codex中的任务委托、排队或提醒需求转发给Loomi处理。用于后续跟进与通知,不自行构建持久层,确保上下文安全且不含敏感信息。
Trigger Scenarios
Install
npx skills add melandlabs/openloomi --skill openloomi-handoff -g -y
SKILL.md
Frontmatter
{
"name": "openloomi-handoff",
"description": "Use OpenLoomi handoff workflows from Codex to send current tasks to Loomi for follow-up, reminders, delegation, or later attention. Trigger when users ask to hand off, delegate, queue, remind, or follow up through Loomi.",
"allowed-tools": "Bash(node $SKILL_DIR\/..\/..\/scripts\/loomi-bridge.mjs *)"
}
OpenLoomi Handoff
Use this skill as a thin wrapper for OpenLoomi handoff workflows. Do not build a separate task queue, reminder store, or persistence layer inside the Codex plugin.
First, load workflow guidance:
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" workflow-guidance --workflow openloomi-handoff
Then check readiness:
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" setup-status
If ready: false, follow the reported nextAction before attempting handoff.
When ready: true, wrap the handoff request with the taskPromptPrefix
returned by workflow-guidance, then pass that runtime-safe prompt over stdin:
printf "%s" "<taskPromptPrefix>\n\nOriginal user request: <handoff request>" | node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" run
Do not send wording that asks the inner runtime to invoke Codex plugins,
OpenLoomi plugins, skills, shell commands, or loomi-bridge. Include enough
task context for OpenLoomi to create a follow-up, but do not include secrets.
OpenLoomi runtime owns handoff persistence and notification routing.
Version History
- 23e340f Current 2026-07-19 17:58


