agentleFS
OpenCovenOpenCoven/coven/skills/coven-board-entry/SKILL.md

coven-board-entry

Skill75 starsChanged 4 months agoMITView on GitHub

Purpose: Create a new task on the Coven task board programmatically. Any familiar can use this without knowing task service internals. Returns the created CovenTask object as JSON. Or via the JS API (ESM): Canonical source: OpenCoven/coven/skills/coven-board-entry/ This skill is symlinked into harnesses and familiar workspaces from the canonical location. Do not edit copies — edit the source. Active symlinks: - ~/.openclaw/workspace/echo/skills/coven-board-entry → canonical - cast-codes/.agents/skills/coven-board-entry → canonical (Codex/Claude harness) - cast-codes/.warp/skills/coven-board-entry → canonical (Warp harness) - ~/.openclaw/skills/coven-board-entry → canonical…

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Purpose: Create a new task on the Coven task board programmatically.

    line 3

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Skill: coven-board-entry

Purpose: Create a new task on the Coven task board programmatically. Any familiar can use this without knowing task service internals.

Input

FieldTypeDefaultNotes
titlestringrequiredTask title
descriptionstringoptionalFull description
statusTaskStatus"inbox"inbox / started / completed / blocked
priorityTaskPriority"medium"critical / high / medium / low
familiarstringoptionalFamiliar slug (e.g. "echo")
projectstringoptionalProject name (e.g. "CovenCave")
tagsstring[]optionalArray of tags

Output

Returns the created CovenTask object as JSON.

How it works

  1. Try gateway API first — POST to http://localhost:3000/api/gateway/tasks with task payload
  2. Fallback — If gateway unavailable or fails, write to ~/.openclaw/coven-tasks-pending.json for later sync

Usage (from a familiar / subagent)

# Direct call via the skill script
node /Users/buns/.openclaw/workspace/echo/skills/coven-board-entry/create-task.mjs \
  --title "My new task" \
  --description "Details here" \
  --priority high \
  --familiar echo \
  --project CovenCave \
  --tags memory,ui

Or via the JS API (ESM):

import { createCovenTask } from './create-task.mjs';

const task = await createCovenTask({
  title: "My task",
  priority: "high",
  familiar: "echo",
  project: "CovenCave",
  tags: ["memory"]
});
console.log(task);

Notes

  • IDs are auto-generated as <familiar>-<slug>-<timestamp> or task-<uuid>
  • createdAt / updatedAt are set automatically to current UTC time
  • createdBy defaults to familiar if provided, else "unknown"
  • Pending tasks file: ~/.openclaw/coven-tasks-pending.json

Location & Symlink Convention

Canonical source: OpenCoven/coven/skills/coven-board-entry/

This skill is symlinked into harnesses and familiar workspaces from the canonical location. Do not edit copies — edit the source.

Active symlinks:

  • ~/.openclaw/workspace/echo/skills/coven-board-entry → canonical
  • cast-codes/.agents/skills/coven-board-entry → canonical (Codex/Claude harness)
  • cast-codes/.warp/skills/coven-board-entry → canonical (Warp harness)
  • ~/.openclaw/skills/coven-board-entry → canonical (global OpenClaw)

Adding a new harness symlink:

ln -s /Users/buns/Documents/GitHub/OpenCoven/coven/skills/coven-board-entry \
  /path/to/harness/skills/coven-board-entry

Download now (ZIP)

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.