16 niveles gratuitos disponibles · Skills de Studio gratis durante la beta Empezar desde el nivel 1
newbieskill
newbieskill
Aprender IA
Suite de Despliegue WebSuite de Creación de Contenido ViralSuite de Productividad en la OficinaSuite de Monetización Indie
Skills Precios
Idioma:
English 繁體中文 日本語 Español
Resultado real · comprobaciones registradas Muestra real · Markdown
Recorrido de 30 segundos

TrailNote — launch checklist

Public fictional practice project (launch-a#/fixture). Project: TrailNote (launch-a#/project). Deadline: 2026-11-05 (launch-a#/deadline); time of day and timezone are unknown.

The recorded statuses and checks below come only from the consumed handoff. The underlying work has not been independently verified. Proposed actions remain pending and were not executed.

IDItemOwnerRecorded statusRecorded checkProposed next action (pending)Source
A1landing page copyeditorreadysource claims reviewedNone proposed from this recorded check.launch-a#/items/0
A2product screenshotsdesignerdraftmobile crop still requiredComplete the mobile crop.launch-a#/items/1
A3download packagebuilderreadyfiles compared with manifestNone proposed from this recorded check.launch-a#/items/2
A4checkoutbuildernot-testedno real payment test yetObtain a real payment-test result; no test was performed here.launch-a#/items/3

Unknowns: deadline time/timezone (launch-a#/deadline) and the real payment-test result (launch-a#/items/3/check). Neither is filled in or treated as completed. These unknowns do not prevent producing this checklist.

Provenance: consumed L:/project-folder-2/skillcube/studio/multi-agent/demo/output/worker-a/handoff-a.json; saved result L:/project-folder-2/skillcube/studio/multi-agent/demo/output/worker-b/checklist-a.md. This file records the checklist only; it is not launch approval or evidence that project work was executed.

Muestra presentada exactamente como fue generada Descargar muestra completa
Ejecución Codex Ejecutado por tu Agent; el cómputo de tokens se factura con tu proveedor de modelo
Entorno probado:
Codex · Windows
El Agent y el modelo se facturan según tu proveedor. Los requisitos y servicios adicionales figuran en el paquete.
Two Agent sessions or subagents

En qué fases de la misión principal se usa

Los Skills son tu equipo en el camino del Agent. Conéctalos con la misión principal para dominarlo.

4-1 · Colaboración Multi-Agent →

Continúa con este resultado: Conexión con el Mundo Exterior (MCP) →

✓ Ideal para ti si...
  • Principiantes de IA que aprenden con tareas reales
  • Empieza en la lección correspondiente; visitar una página no equivale a completar la tarea.
⊗ No recomendado para...
  • Operaciones ajenas a la tarea o acceso a cuentas sin autorización
✦ Lo que recibirás
  • Domina la división de tareas y el diseño de entregables intermedios
  • El entregable intermedio tiene nombre, formato y criterios bien definidos
  • El segundo agent completó su parte sin requerir aclaraciones adicionales

Contenido entregado: archivo SKILL.md completo + muestra verificada. Se ejecuta en tu propio AI Agent.

¿Cómo empezar?

Un Skill es un conjunto de reglas que enseña a la IA a completar tareas.

Obtener e instalar ↑
1
Aporta tu material
Divide una tarea entre dos agents (o dos sesiones) comunicándolos mediante un archivo intermedio.
2
Tu Agent sigue las reglas
Domina la división de tareas y el diseño de entregables intermedios
3
Abre y comprueba el resultado
El entregable intermedio tiene nombre, formato y criterios bien definidos
Enviar a tu AI Agent

Usa multi-agent para ayudarme con esta tarea. Pide el material que falte, utiliza herramientas reales, guarda el resultado y compruébalo con los criterios de la lección.

Antes de empezar La evidencia indica su alcance. El modelo y los permisos dependen del Agent. Extraer archivos no demuestra el descubrimiento automático. El Agent y el modelo se facturan según tu proveedor. Los requisitos y servicios adicionales figuran en el paquete.

Empieza a utilizarlo aquí

El zip incluye reglas, biblioteca, scripts, salidas reales y el vídeo de demo; no es solo un archivo de prompt.

Descargar paquete completo (.zip) Descargar SKILL.md
  1. Abre Codex o Claude Code y pega el prompt de instalación.
  2. Deja que el Agent lea y guarde las reglas completas, confirmando su detección.
  3. Copia el ejemplo de uso anterior, añade tus notas y ejecuta.
Instalación manual · Ver SKILL.md completo (81 líneas)

Codex：~/.agents/skills/multi-agent/SKILL.md
Claude Code：~/.claude/skills/multi-agent/SKILL.md

--- name: multi-agent description: Split a concrete task between two explicitly authorized Agents or sessions, exchange a self-contained file handoff and verify the downstream result against the original source. Use for the multi-agent level of the newbieskill main quest. --- # Two Agents, one usable handoff This is main quest level 4-1. The goal is a finished task whose downstream worker can proceed from a clear handoff file. ## Required authorization and inputs Use two Agents only when the user has asked for or authorized that collaboration. Otherwise explain the two-session method without silently creating agents. Use the actual delegated tool when available; two shell processes are not evidence of two model sessions. Keep the task bounded to the user's materials and requested result. ## Define the shared result Write the desired final file, the source material and the checks before splitting work. Choose a dependency boundary: the first worker structures reliable source facts, and the second produces the requested deliverable from that structure. Do not parallelize a dependent operation before its required input exists. Independent tasks can run concurrently when the available tools and authorization permit it. ## Design a self-contained handoff Specify a named file and a stable format, such as JSON with a short explanatory note. Include the task, source identifiers, confirmed facts, unknowns, constraints, requested output and acceptance criteria. Each material fact must identify a source field or row. Do not assume the downstream Agent can see the first worker's chat history. Do not give the workers your intended answer as though it were source evidence. ## First worker Read the source directly and preserve its numbers, statuses and dates. Normalize the material into the agreed handoff. Mark missing information as unknown; do not turn a draft into a finished feature. Check that the handoff is valid and contains what the second worker needs. Save the file before telling the second worker to continue. ## Second worker Read the handoff and the task's constraints. Produce the requested result using those facts only. If an essential input is missing, state the blocker rather than inventing it. Do not contact the original user or another person without separate authorization. Record which input file was consumed and where the result was saved. ## Reconcile the final result The coordinator compares the downstream result with the original source, not only with the intermediate handoff. Check arithmetic, row counts, exact statuses and unsupported claims. Confirm the output includes the requested actions and identifies unknowns. Preserve the original input, both handoffs/results and the actual session/tool receipts. ## Failure handling - Only one Agent is available: explain that this is a single-session rehearsal, not a passed collaboration test. - Empty source: ask for the missing material; no fabricated handoff facts. - Incomplete handoff: return a specific list of missing fields to the first worker. - Conflicting edits: keep worker output directories separate and let the coordinator reconcile. - Downstream result contradicts a source: correct it and repeat the affected check before shipping. ## Self-test tasks 1. Give worker one `inputs/launch-a.json`; worker two uses its handoff to make a launch checklist without reading the original file. Reconcile both against the original. 2. Repeat with `inputs/launch-b.json`, which has different statuses and an unknown date. No deadline or completed feature may be invented. 3. Give worker one `inputs/empty.json`; it must request missing source material rather than generating achievements. Failure means a missing provenance record, an unsupported claim, no actual second session or an unexplained essential downstream question. File-format validation alone cannot prove Agent collaboration. ## Route Return: `/path/multi-agent/`. Next: `/path/mcp-outside/` — connect one explicitly permitted external capability and make a real call. Useful branches include task planning, review and controlled worktree collaboration when those capabilities are actually installed. ## Rights Original newbieskill workflow. Personal and commercial work is permitted; do not resell the complete package.

Preguntas frecuentes antes de empezar (FAQ)

Aclara cualquier duda antes de comprar y ejecútalo sin fricciones.

¿Cómo empiezo? +
Descarga el ZIP completo y entrega el prompt de instalación a tu Agent. Conserva juntos los scripts y las referencias. El modelo se factura por separado.
¿Es gratuito este Skill básico? +
Sí. La misión principal básica es gratuita. Los productos avanzados de Studio mantienen sus propios precios.
Membresía newbieskill

Una solución para cada
tarea repetitiva.

Una suscripción desbloquea todos los Skills de Studio. ¿Solo necesitas este? Consíguelo por separado.

Comparar planes completos
Gratis Colaboración Multi-Agent
Obtener gratis