Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

brag-log

Estrelas4

Forks0

Atualizado11 de julho de 2026 às 21:16

Append accomplishments to your evergreen impact log (brag doc), creating it if absent, so self-reviews and weekly snippets write themselves. With no args, harvest recent wins from your weeklies, completed projects, decisions, and incidents and propose entries to add. Use when the user wants to log a win, update their brag doc / impact log, or record an accomplishment. Pass the accomplishment as args, or none to harvest.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

trustmaster

trustmaster/emos

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Especialistas em gestão de projetosNegócios e Operações Financeiras·SOC 13-1082

SKILL.md

readonly

name

brag-log

description

Maintain the owner's evergreen impact log (brag doc) at {paths.reports}/brag-log.md.

Resolve role first: read owner.role from .agents/config.yaml (default em) and open the role pack at .agents/roles/{role}.md. Use its {{review_dimensions}} to categorize each entry. Also read paths.reports (default 10-reports), owner.name, and owner.slug from config.

Ensure the log exists. If {paths.reports}/brag-log.md is absent, read _templates/impact-log.md and create it, resolving {{owner_name}} / {{owner_slug}} and setting updated: to today.
Gather entries.
- args present — treat args as one accomplishment. Draft a single entry from it; ask for the impact/metrics only if none is stated and none is obvious from context.
- no args — harvest candidates the owner hasn't logged yet:
  - 01-weekly/ — this and last week's #win items and completed deliverables.
  - 03-projects/ — projects where owner == owner.slug with a recent milestone or a completed/paused status change.
  - 04-decisions/ — ADRs the owner authored (deciders includes {{owner_slug}}).
  - 05-incidents/ — incidents the owner owned or helped resolve. Propose the drafted entries and confirm before writing. Skip anything already in the log (match on headline/date).
Draft each entry with: a ### YYYY-MM-DD — headline, the best-fit Dimension from the role's {{review_dimensions}}, What, Impact (numbers when available), Evidence (links to PRs / docs / dashboards / tickets), and optional Recognition.
Prepend entries to the top of the ## Log section (newest first). This is an append-only log — never rewrite or delete existing entries. Set frontmatter updated: to today.

Output the entries added and the log path. Note the log feeds perf-review (self-review) and manager-report (weekly snippets) — the richest single source for both.

Mais deste repositório

mesmo repositório

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

brag-log

description

Maintain the owner's evergreen impact log (brag doc) at {paths.reports}/brag-log.md.

Ensure the log exists. If {paths.reports}/brag-log.md is absent, read _templates/impact-log.md and create it, resolving {{owner_name}} / {{owner_slug}} and setting updated: to today.
Gather entries.
- args present — treat args as one accomplishment. Draft a single entry from it; ask for the impact/metrics only if none is stated and none is obvious from context.
- no args — harvest candidates the owner hasn't logged yet:
  - 01-weekly/ — this and last week's #win items and completed deliverables.
  - 03-projects/ — projects where owner == owner.slug with a recent milestone or a completed/paused status change.
  - 04-decisions/ — ADRs the owner authored (deciders includes {{owner_slug}}).
  - 05-incidents/ — incidents the owner owned or helped resolve. Propose the drafted entries and confirm before writing. Skip anything already in the log (match on headline/date).
Draft each entry with: a ### YYYY-MM-DD — headline, the best-fit Dimension from the role's {{review_dimensions}}, What, Impact (numbers when available), Evidence (links to PRs / docs / dashboards / tickets), and optional Recognition.
Prepend entries to the top of the ## Log section (newest first). This is an append-only log — never rewrite or delete existing entries. Set frontmatter updated: to today.

Output the entries added and the log path. Note the log feeds perf-review (self-review) and manager-report (weekly snippets) — the richest single source for both.