load-profile

Estrellas13

Forks0

Actualizado26 de junio de 2026 a las 10:50

Read the current project's agent-hub profile and orient the team to this project's stack, commands, and conventions. Use at the start of a work session, when the user asks "what stack is this / who's on the team here", or before delegating substantial work.

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.

Ejecutar en Manus

Fuente

berkcangumusisik

berkcangumusisik/agent-hub

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	load-profile
description	Read the current project's agent-hub profile and orient the team to this project's stack, commands, and conventions. Use at the start of a work session, when the user asks "what stack is this / who's on the team here", or before delegating substantial work.

load-profile

Orient to the current project before doing work.

Steps

Read .claude/agent-hub/profile.yml. If it does not exist, tell the user there's no profile and suggest the agent-hub-init skill (or /onboard). Stop.
Read .claude/CLAUDE.md if present for extra context and conventions.
Read any recorded decisions under .claude/agent-hub/decisions/ (the team's memory). Honor accepted ADRs — never silently contradict one.
Summarize back, briefly:
- Project name, type, and stack (language / framework / database).
- The real commands (install/dev/test/lint/build).
- The active team members and what they cover.
- Any conventions, doNot rules, and key decisions on record.
Hold this context for the session. When delegating, only invoke specialists listed in team.active, and pass them the relevant profile facts.

This is the bridge that makes the same super-team behave differently from one project to the next.

Más de este repositorio

mismo repositorio

agent-hub-init

berkcangumusisik/agent-hub

Scaffold the agent-hub project profile (.claude/agent-hub/profile.yml + CLAUDE.md) for the current project so the super-team can specialize to it. Use when a project has no profile yet, or when the user says "onboard", "set up the team here", or "create the profile".

2026-06-2613

decision-log

berkcangumusisik/agent-hub

Record and read architectural decisions (ADRs) for a project so the team's choices persist across sessions. Use when the user says "decide", "record this decision", "why did we choose X", or when a significant technical choice is made.

2026-06-2613

handoff

berkcangumusisik/agent-hub

Produce a concise session handoff so the next session (or teammate) can pick up instantly. Use when the user says "handoff", "wrap up", "summarize where we are", or at the end of a work session.

2026-06-2213

name	load-profile
description	Read the current project's agent-hub profile and orient the team to this project's stack, commands, and conventions. Use at the start of a work session, when the user asks "what stack is this / who's on the team here", or before delegating substantial work.

load-profile

Orient to the current project before doing work.

Steps

Read .claude/agent-hub/profile.yml. If it does not exist, tell the user there's no profile and suggest the agent-hub-init skill (or /onboard). Stop.
Read .claude/CLAUDE.md if present for extra context and conventions.
Read any recorded decisions under .claude/agent-hub/decisions/ (the team's memory). Honor accepted ADRs — never silently contradict one.
Summarize back, briefly:
- Project name, type, and stack (language / framework / database).
- The real commands (install/dev/test/lint/build).
- The active team members and what they cover.
- Any conventions, doNot rules, and key decisions on record.
Hold this context for the session. When delegating, only invoke specialists listed in team.active, and pass them the relevant profile facts.

This is the bridge that makes the same super-team behave differently from one project to the next.