agentleFS
Sign inStart free
MiviaLabsMiviaLabs/mivia-agentkit/.agents/skills/mivia-agent-workflows/SKILL.md

mivia-agent-workflows

Skill2 starsChanged 4 months agoMITView on GitHub

Codex adapter for mivia-agent workflow execution, run artifacts, and desktop-agent workflow routing.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Read .ai/skills/mivia-agent-workflows/SKILL.md first.

    line 14
  2. Very specific:

    Use mivia-agent-report/v1 from .ai/templates/agent-report-v1.md.

    line 16
  3. Distinctive:

    Use the real CLI boundary for workflow proof.

    line 20
  4. Very specific:

    Run mivia-agent run --repo .

    line 21
  5. Very specific:

    Treat .ai/runs/ as ignored runtime output and do not commit run artifacts.

    line 23

≈ “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

Mivia Agent Workflows

Read .ai/skills/mivia-agent-workflows/SKILL.md first. Follow AGENTS.md, .ai/INDEX.md, and docs/desktop-agent-workflows.md.

Use mivia-agent-report/v1 from .ai/templates/agent-report-v1.md; do not define a Codex-specific report shape.

Codex-specific behavior:

  • Use the real CLI boundary for workflow proof.
  • Run mivia-agent run --repo . --workflow <name> --dry-run --json before live workflow execution.
  • Translate user objectives into mivia-agent run --repo . --workflow <name> --var objective="<free-text objective>" --json.
  • Treat .ai/runs/ as ignored runtime output and do not commit run artifacts.
  • Report workflow pass as artifact acceptance only, not ship approval.

AgentKit repo workflows:

  • research-loop
  • bug-audit-loop
  • roadmap-implementation-review-loop
  • desktop-workflow-docs-loop

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.

Check your setup, free