coordinar-un-proceso-de-entrevistas

coordinar-un-proceso-de-entrevistas is a skill for Claude Code, Codex from gethouston/houston. It costs 63 tokens per session (1,576 once invoked), scanned A, original, MIT.

An interview-scheduling workflow that finds times shared by the candidate and the interview panel, prepares an interviewer-specific brief, and produces a proposed schedule. It does not send the invitations.

In plain words
What is it for?
Organizing a candidate’s interview panel, matching calendars, preparing panel materials, and reviewing the proposed timetable.
Why use it?
It reduces the back-and-forth needed to coordinate several people while leaving final confirmation and sending under your control.

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 Organizing a candidate’s interview panel, matching calendars, preparing panel materials, and reviewing the proposed timetable.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gethouston/houston/coordinar-un-proceso-de-entrevistas
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 coordinar-un-proceso-de-entrevistas
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 coordinar-un-proceso-de-entrevistas

README.md
[![agentmods](https://agentmods.dev/badge/skills/gethouston/houston/coordinar-un-proceso-de-entrevistas/github.svg)](https://agentmods.dev/skills/gethouston/houston/coordinar-un-proceso-de-entrevistas)
Your own site
<a href="https://agentmods.dev/skills/gethouston/houston/coordinar-un-proceso-de-entrevistas"><img src="https://agentmods.dev/badge/skills/gethouston/houston/coordinar-un-proceso-de-entrevistas/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 coordinar-un-proceso-de-entrevistas

Your own site · 80×15
<a href="https://agentmods.dev/skills/gethouston/houston/coordinar-un-proceso-de-entrevistas"><img src="https://agentmods.dev/badge/skills/gethouston/houston/coordinar-un-proceso-de-entrevistas.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,576 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.00063 $0.01576
Opus 5 $0.00032 $0.00788
Sonnet 5 $0.00013 $0.00315
Haiku 4.5 $0.00006 $0.00158

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

Security

Grade A, and why

coordinar-un-proceso-de-entrevistas 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/people/.agents/skills/coordinar-un-proceso-de-entrevistas/SKILL.md · 118 lines

How it starts

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

Coordinar un Proceso de Entrevistas

Cuándo usarla

  • Explícito: "programa el proceso de {candidate}", "coordina el panel para {candidate}", "organiza las entrevistas de {candidate}", "agenda el proceso".
  • Requisito previo: el registro del candidato existe y pasó la preselección.
  • Una invocación por proceso de entrevistas de candidato.

Conexiones que necesito

Realizo el trabajo externo a través de Composio. Antes de correr esta habilidad, 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 de Integraciones, y me detengo.

  • Calendario (Google Calendar, Outlook): leer disponibilidad y redactar invitaciones. Obligatoria.
  • Bandeja de entrada (Gmail, Outlook, Loops): redactar el contacto con el candidato con el horario propuesto. Opcional.

Si tu calendario no está conectado, me detengo y te pido que lo conectes desde la pestaña de Integraciones.

Información que necesito

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

  • Registro del candidato: Obligatorio. Por qué lo necesito: no programo un proceso para un candidato que nunca he visto. Si falta, pregunto: "Primero haz una evaluación de este candidato para que sepa que ya pasó el primer filtro."
  • Panel: Obligatorio. Por qué lo necesito: necesito nombres y correos para revisar disponibilidad. Si falta, pregunto: "¿Quién está en el panel? Comparte nombres o correos."
  • Ventana objetivo: Obligatorio. Por qué la necesito: no puedo buscar disponibilidad sin ella. Si falta, pregunto: "¿En qué ventana estamos pensando, por ejemplo, martes a jueves en la tarde de la próxima semana?"
  • Duración por entrevista: Obligatorio. Por qué la necesito: define los horarios que busco. Si falta, pregunto: "¿Cuánto dura cada entrevista, 30, 45 o 60 minutos?"
  • Zona horaria: Obligatoria cuando el panel abarca varias regiones. Por qué la necesito: evita sorpresas a las 6 de la mañana. Si falta, pregunto: "¿Qué zona horaria debo usar como referencia para el proceso?"

Read the full file on GitHub · 118 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 · 118 lines · 63 tokens per session scan A 37cffd43d2e0

Subscribe to this mod's changes

coordinar-un-proceso-de-entrevistas is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 1,576 once invoked, about $0.0003 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.