brag-doc-from-git
Build an Evidence-Based Brag Document from Git
Review preparation is difficult when contributions are scattered across pull requests, commits, and personal notes. This skill groups that evidence into a Markdown draft and marks missing results instead of inventing impact.
使用我的智慧代理安裝
將此請求複製給你的智慧代理,其中包含權威 Skill 頁面和清單。
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.你的智慧代理仍應顯示其計畫,並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時,請使用這些連結。
測試它
正在使用「brag-doc-from-git」。 Sample evidence: PR #42 added retry handling on March 12. No outcome metrics were provided.
預期結果:
- Theme: Reliability
- What I did: Added retry handling.
- Result: [GAP: What changed for users or the team?]
- Evidence: March 12, supplied PR #42 reference.
- Priority question: Do incident records show a change in failed requests after deployment?
正在使用「brag-doc-from-git」。 Sample notes: I owned the cache integration in a team project. User-provided measurements show response time fell from 240 ms to 180 ms.
預期結果:
- Theme: Performance
- What I did: Contributed the cache integration to a team performance project.
- Result: User-provided measurements show response time decreased from 240 ms to 180 ms.
- Scope signal: Owned the cache integration, not the entire project.
- Evidence gap: Add the project link and measurement source.
安全審計
中風險All six static findings are false positives from Markdown delimiters, inline examples, or legitimate review-writing instructions. The authenticated GitHub search lacks repository filters and can retrieve private repository metadata outside the user-approved scope. No evidence found of malicious intent, credential theft, destructive commands, or audit-directed prompt injection.
已確認的安全問題 (1)
風險因素
⚙️ 外部命令 (4)
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據,不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/agentkitco-brag-doc-from-git/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/agentkitco-brag-doc-from-git?utm_source=security_passport_badge)HTML 徽章
<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>學術引用 (APA · BibTeX · CFF)
APA 引用
agentkitco. (2026). brag-doc-from-git security audit report (audit version 2) [Author version 1.0]. Skillstore. https://skillstore.io/skills/agentkitco-brag-doc-from-git/audits/2BibTeX 引用
@techreport{agentkitco-agentkitco-brag-doc-from-git-2026,
author = {agentkitco},
title = {brag-doc-from-git security audit report (audit version 2)},
institution = {Skillstore},
year = {2026},
number = {2},
url = {https://skillstore.io/skills/agentkitco-brag-doc-from-git/audits/2},
note = {Author version 1.0}
}CITATION.cff
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 2)"
version: "1.0"
type: report
authors:
- name: "agentkitco"
date-released: "2026-10-22"
url: "https://skillstore.io/skills/agentkitco-brag-doc-from-git/audits/2"
identifiers:
- type: other
value: "skillstore:agentkitco-brag-doc-from-git:audit:2"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中你可以打造什麼
Prepare a Performance Self-Review
Group recent engineering contributions into evidence-backed themes and identify missing outcomes before submitting a review.
Assemble Promotion Evidence
Organize supported leadership, cross-team work, and technical contributions while preserving accurate ownership and evidence links.
Refresh Resume Accomplishments
Convert verified contributions into resume material and remove confidential details intended only for internal documents.
試試這些提示
Create a brag document for my last six months of work. Ask me which repositories to use before collecting evidence.
Use local Git history in [repository] for [author email] since [date]. Group contributions by theme and mark unknown results as gaps.
Draft my self-review for [date range] using only [approved repositories]. Restrict GitHub queries to those repositories. Include [mentoring and incident notes].
Build a promotion outline from [approved evidence and notes]. Preserve team attribution, distinguish verified outcomes from gaps, and rank missing evidence. Ask three priority questions.
最佳實務
- Agree on the time window and repository list, then add explicit repository filters before running GitHub searches.
- Provide outcome measurements, evidence links, and notes about contributions that Git does not record.
- Review attribution and remove confidential information before sharing the draft outside your organization.
避免
- Treating commit counts or pull request titles as proof of business impact.
- Claiming sole ownership of team results without evidence of your specific contribution.
- Running an unrestricted account-wide search when only named repositories are approved.
常見問題
Which AI tools can use this skill?
Does it require GitHub?
What happens when results are unknown?
Can it include mentoring and incident work?
Will it search only the repositories I name?
What formats can it produce?
開發者詳細資訊
作者
agentkitco授權
MIT
作者版本
v1.0
Skillstore 修訂
r1
版本提示
作者聲明的版本不符合 SemVer 規範。
引用
18efac79a818d7e997295839638fdd21906cfd1c
維護新鮮度
2026/10/22
使用量
5 次下載 · 1 次瀏覽
檔案結構
📄 SKILL.md