agentsclimarketplace

Evidence first workspace setup

Skill x2724009/evidence-first-durable-task-orchestrator/skills/evidence-first-workspace-setup

A Design Gate for complex AI agent work: design first, execute second, preserve evidence always.

Install
npx -y skills add x2724009/evidence-first-durable-task-orchestrator --skill evidence-first-workspace-setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 12 days oldThe repository was created 12 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Initialize or integrate Evidence-First Durable Task Orchestrator in a user-selected project. Use only when the user asks to set up the workflow, choose a task-record location, or add a project AGENTS.md entry. Creates a config file, Markdown task folders, and a suggested AGENTS.md snippet; never overwrites existing project instructions.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.3 KB, 375 tokens by cl100k_base, as published. Nobody here has run it

Evidence-First Workspace Setup

This adapter connects the core workflow to one project without turning personal preferences into global rules. It creates files only after the user identifies the target project and task location.

Preflight

  1. Read existing project instructions and check whether .evidence-first-task.yaml already exists.
  2. Ask where records should live only when the user did not specify it. Recommend .agent-tasks/ in the project for a simple, portable default.
  3. Explain whether task records will be committed or ignored. Do not silently alter .gitignore.
  4. Never infer an Obsidian Vault, home directory, cloud sync folder, or private workspace.

Initialize

Run scripts/init-workspace.sh from the package root with a user-approved project root:

bash scripts/init-workspace.sh --project-root /path/to/project --task-root .agent-tasks

It creates:

<project-root>/
├── .evidence-first-task.yaml
└── .agent-tasks/
    ├── Active/
    ├── Blocked/
    ├── Archive/
    └── AGENTS.integration.md    # suggestion only

The script refuses to overwrite an existing configuration. It never edits or replaces the project's AGENTS.md.

Add the entry gate safely

Read .agent-tasks/AGENTS.integration.md, then propose the relevant block for the existing project AGENTS.md. Only write that project file after the user explicitly approves the exact change. Preserve existing rules and do not add personal task-board paths.

Optional Obsidian

If the user wants Vault browsing, ask for an explicit task_root inside their chosen Vault and then use obsidian-task-board. Do not install Obsidian, Dataview, Sync, or Publish automatically.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.