escribir-un-articulo

escribir-un-articulo is a skill for Claude Code, Codex from gethouston/houston. It costs 99 tokens per session (1,847 once invoked), scanned A, original, MIT.

A help-centre writing tool that turns resolved tickets and product changes into customer-facing documentation. It can also prepare known-issue pages, launch notes for requesting customers, and updates to outdated articles.

In plain words
What is it for?
Use it to document support resolutions, publish known problems, announce requested features, and refresh affected help articles.
Why use it?
It reduces repeated explanations and keeps customers informed when a problem, feature, price, or product behaviour changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to document support resolutions, publish known problems, announce requested features, and refresh affected help articles.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gethouston/houston/escribir-un-articulo
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add gethouston/houston --skill escribir-un-articulo
Clone the repo
git clone --depth 1 https://github.com/gethouston/houston

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for escribir-un-articulo

README.md
[![agentmods](https://agentmods.dev/badge/skills/gethouston/houston/escribir-un-articulo/github.svg)](https://agentmods.dev/skills/gethouston/houston/escribir-un-articulo)
Your own site
<a href="https://agentmods.dev/skills/gethouston/houston/escribir-un-articulo"><img src="https://agentmods.dev/badge/skills/gethouston/houston/escribir-un-articulo/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for escribir-un-articulo

Your own site · 80×15
<a href="https://agentmods.dev/skills/gethouston/houston/escribir-un-articulo"><img src="https://agentmods.dev/badge/skills/gethouston/houston/escribir-un-articulo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 99 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,847 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00099 $0.01847
Opus 5 $0.00049 $0.00924
Sonnet 5 $0.00020 $0.00369
Haiku 4.5 $0.00010 $0.00185

Measured 9d ago against content hash 74756756c141, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

escribir-un-articulo scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

store/agents-i18n/es/support/.agents/skills/escribir-un-articulo/SKILL.md · 119 lines

How it starts

The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Escribir un artículo

Un solo Skill para toda solicitud de redacción del centro de ayuda. Se ramifica según type.

Cuándo usar esto

  • from-ticket: "convierte este ticket en un artículo" / "documenta esta resolución" / "respondí la misma pregunta 3 veces, escribe algo al respecto." Se invoca implícitamente desde flag-a-signal signal=repeat-question cuando un grupo llega a 3 o más casos y no hay un artículo que lo cubra.
  • known-issue: "redacta un documento de problema conocido para {error}" / "es P1, publica una página de estado" / encadenado desde draft-a-playbook.
  • broadcast-shipped: "lanzamos X, avísale a los clientes que lo pidieron" / "envía la nota de 'lo pediste, lo lanzamos'."
  • refresh-stale: "actualiza los artículos afectados por este lanzamiento" / "revisa la documentación, cambiaron los precios" / rutina mensual del centro de ayuda.

Conexiones que necesito

Hago el trabajo externo a través de Composio. Antes de ejecutar este Skill, verifico que las categorías de abajo estén conectadas. Si falta alguna, nombro la categoría, te pido que la conectes desde la pestaña Integraciones, y me detengo.

  • Centro de ayuda (Notion / Google Docs / Help Scout / Intercom), refleja el borrador en tu centro de ayuda publicado. Obligatorio para from-ticket y refresh-stale si quieres que envíe el borrador ahí.
  • Sistema de seguimiento de desarrollo (GitHub / Linear), trae el contexto del error para el documento de known-issue. Obligatorio para known-issue.
  • Bandeja de entrada (Gmail), obtiene el hilo resuelto cuando aún no está en conversations.json. Opcional.

Si pides una página de problema conocido y tu sistema de seguimiento no está conectado, me detengo y te pido que lo conectes.

Información que necesito

Primero leo tu contexto de soporte. Para cada campo obligatorio que falte, hago UNA pregunta en lenguaje sencillo (mejor modalidad: app conectada > archivo > URL > texto pegado) y espero.

  • Plataforma del centro de ayuda, Obligatorio. Por qué lo necesito: el formato y el tono varían según el destino. Si falta, pregunto: "¿Dónde viven hoy tus artículos de ayuda: Notion, Intercom, un sitio de documentación, o en ningún lado todavía?"
  • Muestras de tu voz, Obligatorio. Por qué lo necesito: los artículos del centro de ayuda con el tono equivocado terminan reescribiéndose. Si falta, pregunto: "¿Quieres que analice tu carpeta de enviados para captar el tono, o puedes pasarme de 3 a 5 correos recientes a clientes?"
  • Perfil de tono del centro de ayuda, Opcional. Por qué lo necesito: algunos equipos quieren que el centro de ayuda sea más formal que las respuestas de chat. Si no lo tienes, sigo adelante con "por definir" y uso el mismo tono de tus respuestas.
  • Qué se lanzó, Obligatorio para broadcast-shipped. Por qué lo necesito: no voy a anunciar un vago "lanzamos cosas." Si falta, pregunto: "¿Qué lanzaste? Dame un título y una oración sobre qué hay de nuevo."
  • Qué cambió, Obligatorio para refresh-stale. Por qué lo necesito: reviso los artículos en busca de referencias a lo que cambió. Si falta, pregunto: "¿Qué cambió: precios, el nombre de una función, un flujo de la interfaz, algo más?"

Read the full file on GitHub · 119 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 119 lines · 99 tokens per session scan A 74756756c141

Subscribe to this mod's changes

escribir-un-articulo is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 1,847 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

baoyu-youtube-transcript

A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.

JimLiu/baoyu-skills · 107 tokens

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

instrument-data-to-allotrope

Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…

anthropics/knowledge-work-plugins · 123 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

read

Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…

tw93/Waza · 78 tokens

overleaf-sync

A two-way connection between a local paper folder and Overleaf, a web-based LaTeX editor for writing research papers. It lets you move changes between the local files and the shared Overleaf project.

wanshuiyin/Auto-claude-code-research-in-sleep · 97 tokens