multica-creating-agents

Name: multica-creating-agents
Availability: InStock
Author: waltcow

Document the Multica agent creation contract for CLI and API workflows.

1|Updated May 24, 2026

Search Tags:#security #validation #cli #agent #runtime #creation #multica

Ready to run

npx skills add https://github.com/waltcow/multica --skill multica-creating-agents

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: multica-creating-agents
Source: https://github.com/waltcow/multica/tree/main/server/internal/service/builtin_skills/multica-creating-agents
Command: npx skills add https://github.com/waltcow/multica --skill multica-creating-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Clarifies and codifies how Multica agents are created, including required fields, persistence details, and how secrets and sensitive inputs are gated, so teams have a single reference for provisioning agents.

Core Features & Use Cases

Documents the agent creation contract: fields, validation rules, runtime payload, and security considerations.
Guides debugging and inspection workflows for creating, inspecting, or debugging agents via the CLI or API.
Ensures consistent agent provisioning across environments by outlining defaults, update semantics, and binding behavior.

Quick Start

Review the contract for agent creation and the CLI/API flows to understand required inputs and runtime behavior.

Frequently Asked Questions about multica-creating-agents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What fields are required for Multica agent creation via the CLI or API?▼

Multica agent creation requires specifying fields including name, description, runtime_id, runtime_config, custom_env, custom_args, mcp_config, model, thinking_level, visibility, and max_concurrent_tasks. These define the agent's persisted shape and runtime payload rules for provisioning via the multica CLI or POST /api/agents.

How do I handle secrets and sensitive inputs when creating a Multica agent?▼

Multica agent creation codifies how secrets and sensitive inputs are gated through specific field contracts and update-path semantics. This ensures secure agent provisioning by defining validation rules and security considerations for sensitive data passed via custom_env or runtime_config.

Can I update agent configuration fields after creation using the multica CLI?▼

Yes, Multica agent creation specifies update-path semantics that define how configuration fields like runtime_config, custom_env, and model are modified post-creation. These rules ensure consistent agent provisioning and binding behavior across environments.

What are the default values and validation rules for Multica agent runtime payloads?▼

Multica agent creation defines runtime-payload rules, defaults, and validation constraints for fields like thinking_level, visibility, and max_concurrent_tasks. Engineers and operators use these contracts to ensure consistent agent provisioning and debugging via the CLI or API.

Does the Multica agent creation contract support both CLI and API workflows?▼

Yes, the Multica agent creation contract applies to engineers and operators creating, inspecting, or debugging agents via both the multica CLI and POST /api/agents. It specifies field contracts, runtime-payload rules, and security considerations for consistent provisioning.