Build an Evidence-Based Brag Document
Performance reviews are difficult when accomplishments are scattered across commits, pull requests, and personal notes. This skill organizes that evidence into a Markdown draft and marks missing outcomes for follow-up.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "brag-doc-from-git" from https://skillstore.io/skills/agentkitco-brag-doc-from-git.md and its manifest at https://skillstore.io/api/skills/agentkitco-brag-doc-from-git/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "brag-doc-from-git". Illustrative input: PR #42 added retry handling; no outcome measurements were supplied.
Expected outcome:
Using "brag-doc-from-git". Illustrative input: A team delivered onboarding automation; I implemented validation. Supplied measurements show setup time fell from 40 minutes to 25 minutes.
Expected outcome:
All six static findings are false positives involving Markdown formatting, read-only history queries, or ordinary prose. The GitHub search lacks repository filters and can return private repository metadata outside the named scope, despite an explicit prohibition. No evidence found of malicious exfiltration, destructive commands, or prompt injection.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/agentkitco-brag-doc-from-git/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/agentkitco-brag-doc-from-git?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/agentkitco-brag-doc-from-git?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/agentkitco-brag-doc-from-git/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/agentkitco-brag-doc-from-git.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>agentkitco. (2026). brag-doc-from-git security audit report (audit version 1) [Author version 1.0]. Skillstore. https://skillstore.io/skills/agentkitco-brag-doc-from-git/audits/1@techreport{agentkitco-agentkitco-brag-doc-from-git-2026,
author = {agentkitco},
title = {brag-doc-from-git security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/agentkitco-brag-doc-from-git/audits/1},
note = {Author version 1.0}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "brag-doc-from-git security audit report (audit version 1)"
version: "1.0"
type: report
authors:
- name: "agentkitco"
date-released: "2026-10-17"
url: "https://skillstore.io/skills/agentkitco-brag-doc-from-git/audits/1"
identifiers:
- type: other
value: "skillstore:agentkitco-brag-doc-from-git:audit:1"
description: "Skillstore immutable audit report identifier"
Organize six months of engineering work into themes with supporting links and questions about missing outcomes.
Separate supported ownership and collaboration signals from missing evidence before preparing a promotion packet outline.
Turn shipped work and supplied results into concise resume candidates without inventing metrics or overstating team contributions.
Build my brag document for the last six months using only [owner/repository]. Restrict GitHub searches to that repository and mark missing outcomes.
Use local Git history in [repository] for [author] since [date]. Group accomplishments by theme and include these additional notes: [notes].
Draft a promotion packet outline for [date range] using only [approved repositories]. Apply repository filters, separate individual contributions from team work, and rank evidence gaps.
Use [approved repositories], [date range], and [verified outcomes] to draft a brag document, then adapt it into [self-review or resume bullets]. Restrict all searches to approved repositories. Exclude confidential details, preserve evidence links, and end with the three highest-value questions.
Author
agentkitcoLicense
MIT
Author version
v1.0
Skillstore revision
r1
Version notice
The author-declared version is not valid SemVer.
Ref
743429f75b17204d47661a86b577a575ad67517f
Maintenance freshness
10/17/2026
Usage
0 downloads · 0 views
File structure
📄 SKILL.md
Debug Failures With Reproducible Evidence
Bug fixes based on guesses can miss the cause and introduce regressions. This skill guides reproduction, hypothesis testing, focused fixes, and verification with recorded evidence.
Verify Tests Ran Before Reporting Completion
Completion claims can hide skipped tests, stale results, or checks that never exercised a change. This skill guides fresh verification and reports evidence for each claim.
Write Pull Request Descriptions From Real Changes
Reviewers need clear explanations of changes, testing, and risk. This skill turns Git diffs and commits into structured pull request descriptions grounded in available evidence.
Upgrade Dependencies With Release Note Verification
Dependency upgrades can introduce breaking changes and obscure existing failures. This skill guides focused upgrades through release notes, baseline checks, targeted edits, and verification reports.
Preserve Progress Across Agent Sessions
Long sessions and agent changes can lose important project context. This skill creates a concise handoff with verified state, decisions, and ordered next steps.
Review Code Changes for Security Risks
Security defects can hide in small changes to input handling, authentication, and configuration. This skill guides scoped code triage with evidence, realistic severity, and actionable fixes.
Organize GitHub Issues With Labels
by C0ntr0lledCha0s
Large repositories can lose track of issue priority, scope, and release status. This skill designs label taxonomies, applies labels in bulk, and manages milestones with GitHub CLI workflows.
Draft and Publish Clear GitHub Issues
by equinor
Unclear issue requests create rework, duplicates, and weak acceptance criteria. This skill produces reviewed GitHub issues with consistent structure and controlled publishing.
Publish Agent Skills Across Marketplaces
by ralyodio
Publishing a skill across agent marketplaces requires consistent metadata, clean source links, and platform-specific steps. This skill guides safe packaging, uGig publishing, sh1pt promotion, and follow-up marketplace submissions.
Create Sentry-Style Pull Requests
by getsentry
Writing clear pull requests takes context and review discipline. This skill guides Claude, Codex, and Claude Code through Sentry-style PR preparation.
Master Advanced Git Workflows
by AutumnsGrove
Complex Git maintenance can make history changes and conflict resolution difficult. This skill provides structured guidance, recovery steps, and an optional local helper for common advanced workflows.
Create Consistent GitHub Issues
by C0ntr0lledCha0s
Poorly structured issues create ambiguity and require manual cleanup. This skill drafts and validates titles, bodies, labels, milestones, projects, and relationships.