Skip to content
Agentmart
Submit a tool

starlight-execution

Convert objectives into governed work items and move existing work through explicit states when the user asks to plan, assign, start, block, complete, or…

Skill by frankxai

IndexedMIT★ 11
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/frankxai-starlight-execution

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Convert objectives into governed work items and move existing work through explicit states when the user asks to plan, assign, start, block, complete, or cancel execution.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/starlight-execution

What's inside

Skill name
starlight-execution
Description
Convert objectives into governed work items and move existing work through explicit states when the user asks to plan, assign, start, block, complete, or cancel execution.
License
MIT
Instructions
13 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • openai.yaml · agents/

SKILL.md (first lines)

# Starlight Execution

Treat the execution graph as authoritative business state.

- Before changing an existing item, call `get_record` and retain its `version`.
- Use `create_work_item` for a discrete outcome with one accountable owner. Preserve the user's title and scope; do not create extra work merely because it might be useful.
- Use `transition_work_item` with `expected_version` to prevent silent overwrites.
- A transition to `done` or `cancelled` is consequential. Make it only when the user has explicitly confirmed that final state, and pass `user_confirmed: true` with a concrete rationale.
- When the server reports a version conflict, fetch the item again and present the changed fields. Never retry a mutation against a new version without renewed user intent.

Report the resulting record ID, state, owner, due date, and revision. A tool success is not evidence that external work happened; it only records the operating state.

From frankxai/Starlight-Intelligence-System, MIT.

More from frankxai/Starlight-Intelligence-System

Signals

Stars
11
Forks
3
Open issues
61
Last commit (this folder)
Sep 6, 2026 (1 month ago)
Last release
Jun 10, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from frankxai

Cite this page

starlight-execution skill. Agent Mart. https://agentmart.dev/skills/frankxai-starlight-execution (last updated 2026-10-24)