docs: add an explainer for the boundaries between prompts, plugins/skills, custom scripts, and agent execution

Abierto
#1,026 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
markdown

Línea de trabajo

Start by reading the Automations Overview and Agent Canvas managing-automations pages, then compare their terminology with extensions#816 and OpenHands#16412. Draft a comparison and decision table covering prompts, plugin-based and plugin-spec automations, custom scripts, skills, and agent execution. Done means the new page or section is cross-linked from both docs pages and uses taxonomy consistent with extensions#816.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

priority:medium
Problem or Motivation

A user interview with a CTO and self-described power user showed they struggled to understand the boundaries between prompts, plugins/skills, custom scripts, and agent execution — even while evaluating automations in Agent Canvas. The concepts are each documented somewhere, but no page explains when to use which and how they compose.

Desired Behavior

Add a single docs page (Agent Canvas > Automations, or a concepts page) that explains, at a glance:

  • Prompt-based automations — natural-language scheduled tasks; best for reports, monitoring, one-off LLM work.
  • Plugin-based automations / plugin presets — automations that bundle plugins providing skills or capabilities; the extensions catalog path.
  • Plugin-spec automations — reusable, code-backed, deterministic automations packaged as executable plugins (being documented in OpenHands/extensions#816 / PR #794).
  • Custom scripts (.automation.json / tarball presets) — full packaging control and SDK lifecycle.
  • Skills vs plugins — what each is, where they live (scopes), and how they relate to automations and agent execution.

Include a comparison/decision table (similar in spirit to AmpCode's skills-locations table referenced in OpenHands/OpenHands#16412) and link it from:

  • The Automations Overview page
  • The Automations dashboard "Learn more" target
  • OpenHands/OpenHands#16412's skills/plugins clarity work
Acceptance Criteria
  • A new page (or clearly marked section) explaining the boundaries and when to use each.
  • Cross-linked from the Automations docs and the Agent Canvas managing-automations page.
  • Reviewed for consistency with extensions#816's plugin-spec documentation (same taxonomy, not competing ones).
References
  • OpenHands/OpenHands#16412 (skills & plugins scopes consistency)
  • OpenHands/extensions#816 (plugin-spec docs)
  • OpenHands/OpenHands#16571 (SDLC automations guide)

This issue was created by an AI agent (OpenHands) on behalf of Graham Neubig.

Lenguaje dominante
MDX
Estrellas
19
Forks
104
Merge medio
2 d 12 h
PR fusionados (30 d)
80

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenHands/docs

Todos los issues de OpenHands/docs

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.