Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Plugin-authoring guidance caps skill length at 500 lines but sets no maximum line length

Abierto
  • ¿Algo no está bien?
#113 1 comentario 2 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Área
documentation

Línea de trabajo

Start by comparing the 500-line guidance in progressive-disclosure.md and cowork-specific-skill-instructions.md with agent-building-guidelines/agent-description-length.md. Decide whether to use line, character, or token limits, which files they cover, and whether they are enforced or recommended. Done means the guidance has a consistent, explicit policy for skills, agents, and references.

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

Descripción

Summary

The plugin-authoring guidance caps SKILL.md length at 500 lines but sets no maximum line length. Agent guidance is looser still: it has no body line-count cap or line-length rule at all, only a frontmatter description character budget.

Where the cap lives

  • han-plugin-builder/skills/guidance/references/skill-building-guidance/progressive-disclosure.md (line 36) — "keep the SKILL.md body under 500 lines... Treat 500 lines as the ceiling, not the target." No line-length rule.
  • han-plugin-builder/skills/guidance/references/skill-building-guidance/cowork-specific-skill-instructions.md (lines 167, 249) — repeats the 500-line cap. No line-length rule.
  • han-plugin-builder/skills/guidance/references/agent-building-guidelines/ — the only length guidance is agent-description-length.md (description char budget: 1024 target, ~1500 hard signal). No body line-count or line-length rule for agents.

Why it matters

The 500-line cap exists to bound how much content a skill loads into the model's context window and to keep bloaty skills from distracting agents. But a line is unbounded in length, so a line-count cap alone is a leaky proxy for content volume: 500 very long lines can blow past the intended budget. Without a line-length bound (or a more direct measure), the 500-line ceiling doesn't reliably do the job it exists for.

Open question

Not just "what max line length" — the real question is which lever is right:

  • a per-line character cap (e.g. 80 / 100 / 120, or semantic line breaks / one sentence per line), or
  • a total character or token budget that measures content volume directly, or
  • keeping the line-count cap and adding a line-length bound so it stops being a leaky proxy.

Scope to decide alongside it: does it apply to agent bodies and references/ files too, not just SKILL.md? Hard cap or recommendation? A judgment call, or something a formatter/linter enforces?

Lenguaje dominante
Shell
Estrellas
275
Forks
23
Merge medio
1 d 8 h
PR fusionados (30 d)
12

Preparar el entorno

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 testdouble/han

Todos los issues de testdouble/han

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.