scout-prioritization

Estrellas1

Forks0

Actualizado8 de julio de 2026 a las 17:21

Decide whether a concept is worth working on. Used by Atlas+Scout primitives.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

jar-reis

jar-reis/hermes-skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Especialistas en gestión de proyectosOperaciones empresariales y financieras·SOC 13-1082

SKILL.md

readonly

name	scout-prioritization
description	Decide whether a concept is worth working on. Used by Atlas+Scout primitives.
version	1.0.0
author	Hermes
license	MIT
metadata	{"hermes":{"tags":["prioritization","decision-making","ideation"],"related_skills":["atlas-chunking","brainstorming"]}}

Scout Prioritization

Overview

Decide whether a concept (or its chunks) is worth working on. Second half of the Atlas+Scout compounding primitive (Nate's AI Meeting Takeaways).

Use Case: Prototype Nate's primitives for fleet-wide adoption (e.g., "Prioritize 'source-of-truth discipline' for implementation").

Input/Output

Input: A concept or chunk (e.g., "AI-enabled acquisitions: ownership structure"). Output: Prioritization score (1–5) + rationale.

Procedure

Assess: Evaluate alignment, feasibility, and impact.
Score: Assign 1–5 (1 = low, 5 = high).
Rank: When producing a prioritized list for downstream automation, avoid ties. Use specificity, immediacy, and fit to the user's active systems as tie-breakers.
Rationale: Explain the score with concrete references to the concept/chunk and the user's likely implementation surface.

Example

delegate_task(
    goal="Prioritize 'AI-enabled acquisitions: ownership structure'",
    context="Use the Scout prioritization pattern: score 1–5 + rationale.",
    toolsets=['terminal']
)

Verification

Score: 1–5, no ties.
Rationale: Specific, not generic.
Output: JSON format (for downstream automation).

Más de este repositorio

mismo repositorio

cloudflare-one

jar-reis/hermes-skills

Guides Cloudflare One Zero Trust and SASE work across Access, Gateway, WARP, Tunnel, Cloudflare WAN, DLP, CASB, device posture, and identity. Use when designing, configuring, troubleshooting, or reviewing Cloudflare One deployments. Retrieval-first: use current Cloudflare docs/API schemas instead of embedded product docs.

2026-07-161

cron-automation

jar-reis/hermes-skills

Use when scheduling recurring polls, read-only monitors, or background jobs that must survive shell session boundaries.

2026-07-161

skill-library-management

jar-reis/hermes-skills

Discover, register, and maintain Hermes skills from non-default paths (plugin directories, external repos, shared vaults). Use when skills are missing from `skills_list()`, when the user mentions plugin skills, when symlinking skills, or when reconciling duplicate/overlapping skills between the default tree and external sources.

2026-07-151

antigravity-cli

jar-reis/hermes-skills

Operate the Antigravity CLI (agy): plugins, auth, sandbox.

2026-07-151

stream-retry-tuning

jar-reis/hermes-skills

Tune HERMES_STREAM_RETRIES for mid-stream reconnect resilience.

2026-07-081

telegram-parallel-sessions

jar-reis/hermes-skills

Manage parallel Hermes sessions in Telegram topics.

2026-07-081

name	scout-prioritization
description	Decide whether a concept is worth working on. Used by Atlas+Scout primitives.
version	1.0.0
author	Hermes
license	MIT
metadata	{"hermes":{"tags":["prioritization","decision-making","ideation"],"related_skills":["atlas-chunking","brainstorming"]}}

Scout Prioritization

Overview

Decide whether a concept (or its chunks) is worth working on. Second half of the Atlas+Scout compounding primitive (Nate's AI Meeting Takeaways).

Use Case: Prototype Nate's primitives for fleet-wide adoption (e.g., "Prioritize 'source-of-truth discipline' for implementation").

Input/Output

Input: A concept or chunk (e.g., "AI-enabled acquisitions: ownership structure"). Output: Prioritization score (1–5) + rationale.

Procedure

Assess: Evaluate alignment, feasibility, and impact.
Score: Assign 1–5 (1 = low, 5 = high).
Rank: When producing a prioritized list for downstream automation, avoid ties. Use specificity, immediacy, and fit to the user's active systems as tie-breakers.
Rationale: Explain the score with concrete references to the concept/chunk and the user's likely implementation surface.

Example

delegate_task(
    goal="Prioritize 'AI-enabled acquisitions: ownership structure'",
    context="Use the Scout prioritization pattern: score 1–5 + rationale.",
    toolsets=['terminal']
)

Verification

Score: 1–5, no ties.
Rationale: Specific, not generic.
Output: JSON format (for downstream automation).