Skip to content
Back to skills

Execute

ASecurity

Execute a claimed Fakoli State work packet, verify its acceptance criteria and submit concrete evidence for review.

  • 4 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 6, 2026
ai-agentsgitapidatabase

Works with

  • cli
  • api
  • mcp

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 6, 2026

npx -y skills add fakoli/fakoli-plugins --skill execute --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Execute?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Execute
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/fakoli-execute-fakoli-plugins/badge)](https://www.skillsdirectory.com/skills/fakoli-execute-fakoli-plugins)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: execute
description: "Execute a claimed Fakoli State work packet, verify its acceptance criteria and submit concrete evidence for review."
---

# Execute

Resolve this plugin's installed root from the loaded skill path. Prefer its `bin/fakoli-state` launcher when no matching CLI is on PATH; run from the user's project or pass the command's `--cwd` argument. Read `--help` when a flag is uncertain. Use only tools exposed by the current host. For native MCP calls, supply the target project's absolute `cwd`; the server's startup directory is the installed package.

1. Confirm an active claim and its actor, worktree, scope and expiry. Generate `packet TASK_ID`, then read the returned file; regeneration overwrites the previous packet. `packet TASK_ID --format json` is available for structured consumers.
2. Implement the packet's acceptance criteria. Coordinate overlapping files, preserve other work, and renew the claim before expiry. Use only agent tools and specialist roles exposed in the current host.
3. Run the packet's verification commands and record their actual exits and useful output. Collect changed files from git and any available hook evidence. Hook coverage differs by host; never invent hook-recorded evidence.
4. Run `submit --help`, then submit TASK_ID with the supported evidence flags: `--commands`, `--files-changed`, `--output-file`, optional `--commit-sha`/`--pr-url`/`--screenshots`, and honest `--known-limitations`. Use the CLI's documented value formats. Submission releases the claim and enters review; it is not acceptance.
5. Read `show TASK_ID` to confirm recorded evidence and disposition. Continue to finish when review is in scope.

A passing test is evidence for what it exercised, not proof that an external deployment or API worked. Do not fabricate outputs, silently weaken acceptance criteria, or edit the database directly.

See [README](../../README.md) for setup and the full CLI/MCP surfaces.

Files in this skill

  • SKILL.md1.9 KB
  • agents/openai.yaml124 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.