Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

rebuild

Estrellas4

Forks0

Actualizado10 de julio de 2026 a las 11:13

Regenerate all _index.md dashboard files (weekly, people, projects, decisions, incidents, hiring, strategy) from current content. Use when the user asks to rebuild, refresh, or regenerate the dashboards/indexes. No args needed.

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

trustmaster

trustmaster/emos

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

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	rebuild
description	Regenerate all _index.md dashboard files (weekly, people, projects, decisions, incidents, hiring, strategy) from current content. Use when the user asks to rebuild, refresh, or regenerate the dashboards/indexes. No args needed.

Rebuild all dashboard index files from current content.

Read owner.role from .agents/config.yaml (default em) and open the role pack at .agents/roles/{role}.md for its "Sections in focus / dormant" note. Build every dashboard whose folder has content (they degrade to a minimal placeholder when empty); order and lead with the role's in-focus sections. A role never removes a dashboard — it only changes emphasis.

For each of the following dashboards, scan the relevant content files and generate a fresh _index.md:

01-weekly/_index.md

Scan all 01-weekly/YYYY-Www.md files. Build a table with: Week, Status, completion rate (count [x] vs [ ]), and any #blocked items. Highlight the current active week.

02-people/_index.md

Scan all 02-people/profiles/*.md. Build a roster table: Name, Role, Relation, Level, Status. Show the Skill/Will rating only for people with relation: report (blank otherwise). Note anyone with status other than active. Also list 1-on-1 cadence (count files per person in one-on-ones/).

03-projects/_index.md

Scan 03-projects/*/ (each subfolder except archive/), read the hub {slug}.md file inside. Group by status (Active · Proposed · Paused · Completed · Cancelled). For each project list: name (linked to the hub doc), priority, quarter, and a Jira epic link if jira_epic is set. Then scan 03-projects/archive/*/ into a Completed/Archive table. Do not touch the  blocks inside hub docs — those are owned by project-sync.

04-decisions/_index.md

Scan 04-decisions/*.md. Build a table: ADR ID, Title, Status, Date, Deciders. Group by status.

05-incidents/_index.md

Scan 05-incidents/*.md. Build a table: Date, Title, Severity, Status, Owner. Sort by date descending. Flag any not yet reviewed.

06-hiring/_index.md

Scan 06-hiring/positions/*.md and interviews/*.md. Build: open positions table and candidates-in-flight table with stage and recommendation.

07-strategy/_index.md

Scan 07-strategy/okrs/*.md and roadmaps/*.md. Summarize active OKRs with status and key results count. List roadmap files.

After regenerating each file, confirm the path and a one-line summary of what changed. If a directory has no content files, write a minimal placeholder.

Más de este repositorio

mismo repositorio

create-github-issue

trustmaster/emos

Create a new GitHub issue (optionally added to a GitHub Project board) following the project's standard format — gathers the details, shows a draft for confirmation, then creates it via the `gh` CLI. Use when the user wants to file, open, or create a GitHub issue. Optionally pass the repo and/or issue title as args.

2026-07-164

github-browse

trustmaster/emos

Explore a remote GitHub repository read-only via the `gh` CLI — search code, read a file at a ref, view repo structure, trace the history/PRs touching a path, and blame lines. Use when investigating an incident or working an assignment against code you don't have checked out, across one or more repos. Pass the repo(s) (`owner/repo`) and what you're looking for as args.

2026-07-164

github-pr-fetch

trustmaster/emos

Fetch a GitHub pull request as a structured bundle (metadata, diff, changed files with stats, commits, CI/check status, and existing review comments) via the `gh` CLI. Transport-only — it retrieves, it does not judge. Used by the tool-agnostic `pr-review` skill; you normally won't invoke it directly. Pass a PR number, URL, or branch (and optionally `owner/repo`) as args.

2026-07-164

github-sync

trustmaster/emos

Sync a GitHub Project board into an emOS report grouped by status. Use when the user wants an up-to-date snapshot of a GitHub Projects (v2) board pulled into 10-reports/. Optionally pass a project number/URL, an owner, or a status filter as args.

2026-07-164

pr-review

trustmaster/emos

Do a first-line review pass on a pull request — summarize the changes, flag obvious issues, highlight architectural/dependency changes, and escalate what needs human attention. It hands you structured input to act on; it does NOT auto-approve or post to the code host. Use when the user wants a PR reviewed, triaged, or summarized before they dig in. Pass a PR number, URL, or branch as args.

2026-07-164

import-url

trustmaster/emos

Import any document by URL into emOS. Detects the transport (Confluence, Google Docs, GitHub, or a generic web page), delegates to the medium-specific provider skill when its capability is configured, classifies the content, files it, and pulls any action items assigned to the owner into the current week's plan. Use when the user gives a URL and wants its content brought into the vault. Pass the URL (and optionally a hint about the doc type) as args.

2026-07-124

name	rebuild
description	Regenerate all _index.md dashboard files (weekly, people, projects, decisions, incidents, hiring, strategy) from current content. Use when the user asks to rebuild, refresh, or regenerate the dashboards/indexes. No args needed.

Rebuild all dashboard index files from current content.

For each of the following dashboards, scan the relevant content files and generate a fresh _index.md:

01-weekly/_index.md

Scan all 01-weekly/YYYY-Www.md files. Build a table with: Week, Status, completion rate (count [x] vs [ ]), and any #blocked items. Highlight the current active week.

02-people/_index.md

03-projects/_index.md

04-decisions/_index.md

Scan 04-decisions/*.md. Build a table: ADR ID, Title, Status, Date, Deciders. Group by status.

05-incidents/_index.md

Scan 05-incidents/*.md. Build a table: Date, Title, Severity, Status, Owner. Sort by date descending. Flag any not yet reviewed.

06-hiring/_index.md

Scan 06-hiring/positions/*.md and interviews/*.md. Build: open positions table and candidates-in-flight table with stage and recommendation.

07-strategy/_index.md

Scan 07-strategy/okrs/*.md and roadmaps/*.md. Summarize active OKRs with status and key results count. List roadmap files.

After regenerating each file, confirm the path and a one-line summary of what changed. If a directory has no content files, write a minimal placeholder.