openloomi-goals

Inspect OpenLoomi Goals and their ordered steps via a read-only local API client.

1.0k|46|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/melandlabs/openloomi --skill openloomi-goals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openloomi-goals
Source: https://github.com/melandlabs/openloomi/tree/main/skills/openloomi-goals
Command: npx skills add https://github.com/melandlabs/openloomi --skill openloomi-goals

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Agents working alongside OpenLoomi need visibility into what Goals are active and how far each one has progressed, but there is no built-in way to query that state from outside the app. This Skill provides a read-only client that lists active, paused, or blocked Goals and retrieves a Goal's ordered steps and current progress.

Core Features & Use Cases

  • List Goals: Query all active, paused, or blocked Goals across the current owner's chats, or filter by a specific runtime session ID.
  • Inspect Goal Details: Retrieve a single Goal's ordered steps and progress using its runtime session ID and Goal ID.
  • Use Case: While running an agent session, ask which Goals are currently blocked, get their IDs, then inspect a specific Goal's steps to decide what to work on next.

Quick Start

Ask the agent to list my active OpenLoomi Goals and show the progress of the one I specify.

Frequently Asked Questions about openloomi-goals

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list active OpenLoomi Goals from an agent?

Run node scripts/openloomi-goals.cjs list from the skill directory to return active, paused, or blocked Goals across the current owner's chats. Pass a runtime session ID as an argument to filter results to one session.

How do I check a Goal's steps and progress in OpenLoomi?

Run node scripts/openloomi-goals.cjs get with the runtime session ID and Goal ID returned by the list command. The client calls the local OpenLoomi API and prints the Goal's ordered steps and current progress as JSON.

Can this skill modify or update OpenLoomi Goal state?

No, the client is strictly read-only and only exposes list and get commands. OpenLoomi remains the source of truth for planning, runtime selection, and all lifecycle changes.

Why does the OpenLoomi Goals client fail to connect?

The client requires a running local OpenLoomi server on the default ports or a custom URL set via OPENLOOMI_BASE_URL. It also reads an auth token from ~/.openloomi/token, so OpenLoomi must be installed and authenticated.

Does the OpenLoomi Goals client need external npm dependencies?

No, the script uses only Node.js built-in modules such as fs, os, path, and the global fetch API. Any modern Node.js runtime can execute it without installing packages.