← Back to Skills Marketplace
🔌

Harvest

by OOMOL · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
25
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install oo-harvest
Description
Harvest (getharvest.com). Use this skill for ANY Harvest request — reading, creating, updating, and deleting data. Whenever a task involves Harvest, use this...
README (SKILL.md)

Harvest

Operate Harvest through your OOMOL-connected account. This skill calls the harvest connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Category: Productivity. Exposes 15 action(s).

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Harvest. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "harvest" --action "\x3Caction_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "harvest" --action "\x3Caction_name>" --data '\x3Cjson>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with oo connector schema before constructing --data.

Available actions

Safety

  • Read actions (get / list / search) are safe to run directly.
  • Create, update, send, or post actions change Harvest state — confirm the exact payload and effect with the user before running.
  • Delete or remove actions are destructive — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: \x3Chttps://cli.oomol.com/install-guide.md>):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
    
    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
    
  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login
    
  • scope_missing / credential_expired / app_not_ready / app_not_found — Harvest is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2, API key) at:

    https://console.oomol.com/app-connections?provider=harvest
    
  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

Usage Guidance
Install only if you intend to let OOMOL/Codex operate your connected Harvest account. Review write and delete requests carefully, because the skill can change or remove Harvest time-entry data after you approve the specific action.
Capability Tags
requires-sensitive-credentials
Capability Assessment
Purpose & Capability
The skill can read Harvest account data and create, update, stop, restart, or delete time entries, but those capabilities match its stated Harvest productivity purpose and are explicitly listed.
Instruction Scope
Instructions are scoped to the OOMOL `oo` CLI Harvest connector, require schema inspection before calls, and require user confirmation before write or destructive actions.
Install Mechanism
The skill itself is markdown-only and allows `Bash(oo *)`; its first-time setup text references official-looking OOMOL CLI install and login steps only when required by an auth or missing-command failure.
Credentials
The requested environment access is limited to running `oo` connector commands for Harvest rather than broad shell, filesystem, browser, or local credential access.
Persistence & Privilege
It uses server-managed OOMOL credentials for a connected Harvest account, which is sensitive but disclosed and purpose-aligned; no background persistence, hidden workers, or local credential harvesting is present.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install oo-harvest
  3. After installation, invoke the skill by name or use /oo-harvest
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of `oo-harvest`, a Harvest skill for operating a connected Harvest account through the OOMOL `oo` CLI and server-managed credentials. - Adds time-entry workflows: create, list with filters, retrieve, update, stop, restart, and delete Harvest time entries. - Supports account lookup actions for the current user, clients, projects, tasks, and project task assignments. - Provides per-action reference files with schema-inspection and execution commands for reliable connector usage. - Defines safety guidance for read, write, and destructive actions, including confirmation requirements before changing or deleting Harvest data.
Metadata
Slug oo-harvest
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Harvest?

Harvest (getharvest.com). Use this skill for ANY Harvest request — reading, creating, updating, and deleting data. Whenever a task involves Harvest, use this... It is an AI Agent Skill for Claude Code / OpenClaw, with 25 downloads so far.

How do I install Harvest?

Run "/install oo-harvest" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Harvest free?

Yes, Harvest is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Harvest support?

Harvest is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Harvest?

It is built and maintained by OOMOL (@oomol); the current version is v1.0.0.

💬 Comments