machina-sports/machina-templates · Archived

mkn-constructor

Discover and use this skill for create, scaffold, update, validate, analyze, trace, debug, install, and maintain requests involving Machina agents, agent templates, workflows, connectors, prompts, mappings, documents, skills, and MCP-backed template installation.

First seen Feb 18, 2026

Installation

$ npx skills add machina-sports/machina-templates --skill mkn-constructor

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from machina-sports/machina-templates.

npx skills add machina-sports/machina-templates

Browse all from machina-sports/machina-templates

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
License LICENSES
Default branch main
Open issues 1
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,525 B
  • docs SUMMARY.md 286 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 10 installs

SKILL.md

Machina Agent Builder (Deprecated Alias)

Deprecated: mkn-constructor is a compatibility alias. Use machina-agent-builder for all new work.

End-to-end skill for building, validating, installing, debugging, and maintaining Machina agent templates and their complete resource graphs.

References

Procedural guides for each lifecycle stage:

Reference Description
[init.md](references/init.md) Scaffold new template project from scratch
[create.md](references/create.md) Generate individual YAML components
[validate.md](references/validate.md) Check YAML files against correct patterns
[install.md](references/install.md) Import templates via MCP (local or Git)
[analyze.md](references/analyze.md) Analyze template structure and dependencies
[trace.md](references/trace.md) Trace agent execution chain with variable propagation
[secrets.md](references/secrets.md) Configure vault secrets for connectors
[api.md](references/api.md) MCP operations for all entities (CRUD, execute, search)
[yaml-reference.md](references/yaml-reference.md) Complete YAML syntax and patterns
[connectors.md](references/connectors.md) Current repository inventory and selected guidance

Schemas

Schema and reference patterns grounded in current repository examples:

Schema Entity
[agent.md](schemas/agent.md) Agent definition
[connector.md](schemas/connector.md) Connector (PyScript + REST API)
[document.md](schemas/document.md) Document task type
[mapping.md](schemas/mapping.md) Data transformation mapping
[prompt.md](schemas/prompt.md) Prompt definition + JSON Schema
[setup.md](schemas/setup.md) install.yml + index.yml
[skill.md](schemas/skill.md) SDK skill registration
[workflow.md](schemas/workflow.md) Workflow + task types

Intent Routing

When the user triggers this skill, load the appropriate reference:

User Says Reference
"init template", "scaffold template", "new template project" [init.md](references/init.md)
"create agent", "create workflow", "update prompt", "maintain mapping", "scaffold YAML" [create.md](references/create.md)
"validate", "check YAML", "verify template" [validate.md](references/validate.md)
"install", "import", "deploy template" [install.md](references/install.md)
"analyze", "what's in this template", "overview" [analyze.md](references/analyze.md)
"trace", "execution chain", "variable flow", "debug agent" [trace.md](references/trace.md)
"secrets", "credentials", "configure API key" [secrets.md](references/secrets.md)
"API", "MCP operations", "search agents", "execute workflow" [api.md](references/api.md)
"YAML syntax", "task types", "expression syntax", "foreach" [yaml-reference.md](references/yaml-reference.md)
"connectors", "list connectors", "connector docs" [connectors.md](references/connectors.md)
"report bug", "found issue", "feedback", "suggest improvement" Show Feedback & Contributing section below

For YAML field specifics, read the relevant schema from schemas/.

Workflow

Name: mkn-constructor-check-setup

Validates that the doc-structure document exists and returns its content.

Input Default Description
document_name doc-structure Document to check
Output Description
doc-structure Document content
check-status Workflow execution status

Feedback & Contributing

Found a bug, unexpected behavior, or have an improvement idea while using this skill?

  • Report issues: Open an issue with the label mkn-constructor
  • Contribute fixes: Fork the repo, apply your fix, and open a PR against main
  • What to include: Describe what you expected vs. what happened. For schema/reference fixes, include before/after YAML examples.

When the user encounters an error, unexpected scaffold output, or expresses frustration with a skill behavior, proactively mention this section and suggest opening an issue.

Key Constraints

  • SDK composition only: Use existing MCP/SDK resources only. If an intent cannot be expressed with supported primitives, reject it explicitly; do not generate raw Client API or HTTP proxy code.
  • Connector .py files: No helper functions outside command functions. Each function must be self-contained.
  • Expression syntax: Always use $.get('field') — never ${field} or $field
  • Prompt files: Use prompts: array (not prompt:) with instruction: (not messages:)
  • Connector YAML: Use filetype: (not type:) and filename: (not script:)
  • Install order: connectors → documents → prompts → mappings → workflows → agents → skills
  • Vertex connector policy: Every task connector mapping with name: google-genai and a command must include location: global and provider: vertex_ai in that same mapping.