AutoGineer
Generated banner for Mastra Factory
Generated logo for Mastra Factory

Mastra Factory

MastraOfficialCreated by Mastra

  • Skill
  • Tool integration
  • Automation and integrations
  • Apache-2.0
  • No issues found
Download ZIP

From the author

Operate and supervise Mastra Factory through `mastra api factory`. Use for first-time Factory connection and login, status or queue summaries, project and work-item inspection, thread history and memory, metrics, health, decisions, attention, and user-authorized autonomous or interactive Factory operations on hosted, local, remote, or self-hosted servers.
— the description by Mastra

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The Mastra Factory skill provides a structured interface for interacting with Mastra Factory instances. It enables users to perform operational tasks such as inspecting project states, reviewing work item queues, managing decisions, and monitoring system health. The skill emphasizes a secure, read-only default posture, requiring explicit user authorization for any state-changing mutations. It is designed to work across various deployment types, including local, remote, and self-hosted environments, by leveraging the Mastra CLI for consistent command execution and schema-based interactions.

What it does

  • Connects to and authenticates with Mastra Factory instances.
  • Lists and inspects projects, work items, and their current statuses.
  • Summarizes system health, metrics, and pending human attention items.
  • Executes authorized transitions and updates on work items and decisions.
  • Provides a secure framework for autonomous operations within defined user-granted scopes.
  • Maintains strict safety boundaries by preventing unauthorized access to credentials or sensitive environment data.

When to use it

  • When you need to check the status of a project or work item queue in Mastra Factory.
  • When performing initial setup or connecting to a new Factory instance.
  • When you need to diagnose unhealthy items or review pending decisions.
  • When you have been granted a specific operating scope to automate project transitions or updates.
  • When you need to inspect thread history or agent memory within a Factory session.

Advantages

  • Ensures consistent operational control through a standardized CLI interface.
  • Promotes safety by defaulting to read-only inspection and requiring explicit authorization for mutations.
  • Supports flexible deployment models including local, remote, and self-hosted servers.
  • Reduces manual overhead by allowing for bounded autonomous operations within defined scopes.
  • Provides clear, schema-backed interactions to minimize errors during command execution.

Usage examples

“List all projects in my Factory instance.”
The agent will use the CLI to fetch and display a list of available projects, ensuring the correct URL and organization context are applied.
“Summarize the current status and any blocked work items in project Alpha.”
The agent will inspect the project state, identify active and blocked items, and provide a concise report with a recommended next action.
“Transition work item 123 to the Triage stage.”
The agent will verify the current state, ensure the action is within the authorized scope, perform the transition, and report the updated status.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/mastra-ai/mastra-factory/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip mastra-factory.zip -d .agents/skills

Documentation by Mastra

Mastra Factory

Use mastra api factory as the operational control plane for Factory.

First use: connect before inspecting

Read references/connection.md. Check CLI availability, establish the user's actual Factory URL, and for platform-hosted deployments run mastra auth whoami. If logged out, offer mastra auth login rather than silently starting browser login. Local/self-hosted authentication may differ.

An explicit mastra api --url "$FACTORY_URL" factory project list works from an empty directory; no deployed repository or .mastra-project.json is required. Never assume a shared host, organization, project name, or ID. Preserve the explicit target on subsequent commands.

Default behavior

For status, inspection, diagnosis, queue review, or recommendation requests:

  1. Stay read-only.

  2. Select the sole or explicitly named project; report choices when ambiguous.

  3. Inspect project state, work items, metrics, thresholds, decisions, and attention.

  4. Correlate stages, revisions, sessions, decisions, and attention items.

  5. Report active/queued work, blocked or unhealthy items, running sessions, pending decisions, human attention, and one recommended next action.

  6. Execute a recommendation only when the current request or a previously granted operating scope authorizes it.

Required reference

Read references/factory-cli.md before running Factory commands for output control, contracts, the read-only workflow, mutation protocol, governance constraints, durable-session limitations, and error handling.

For “my work,” actual execution progress, thread messages, memory, or health interpretation, also read references/session-inspection.md. Distinguish card stages from running agents, historical messages from current memory, and agent claims from verified repository outcomes.

Safety boundary

  • Never read or reveal .env, bearer tokens, saved login contents, or platform/provider credentials.

  • Never invent IDs, stages, revisions, request IDs, or sessions.

  • Establish the user's operating scope before mutating. Authorization may cover one action or grant standing autonomy over named projects, resources, action types, or objectives.

  • Within a clear delegated scope, act without asking for confirmation before every mutation. Ask only when an action is ambiguous, outside scope, or materially more destructive than the granted authority.

  • Fetch current state before a write, make the smallest in-scope change, then refetch and report IDs, revisions, and final state.

  • Use transitions—not metadata updates—for stage changes, with the current revision and a fresh UUID request ID.

  • Never use private HTTP routes to bypass unsupported CLI operations.

  • If work-item start lacks a supported durable user session, report the block; never substitute another session or invent a session UUID.

Files

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Mastra
Publisher
Mastra (Official)
Source
mastra-ai/skills · skills/mastra-factory · commit 3020257
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Mastra or Mastra.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download mastra-factory.zip