Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

briefing-documentbriefing document 搜索

Agent Skill

briefing-document 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

480

周安装

20

GitHub Stars

33

下载量

160
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:briefing-document(briefing document 搜索)
来源仓库:https://github.com/mblode/agent-skills
仓库路径:skills/briefing-document
安装命令:
npx skills add https://github.com/mblode/agent-skills --skill briefing-document
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/mblode/agent-skills --skill briefing-document

简介

briefing-document 将多源材料合成为结构化 executive 简报。

  • 提取3-7个核心主题,标注引用来源与页码位置。
  • 适用于战略决策支持与跨部门信息同步。
  • 使用前应确保所有输入材料已脱敏且授权使用。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Briefing Document

Synthesize source materials into a structured, executive-ready briefing.

Workflow

Briefing document progress:
- [ ] Step 1: Gather sources
- [ ] Step 2: Analyze and extract themes
- [ ] Step 3: Write briefing document
- [ ] Step 4: Validate quality

Step 1: Gather sources

Read files, fetch URLs, or accept pasted text. Ask the user for sources if none are provided. Read every source completely before writing anything.

Step 2: Analyze and extract themes

  • Identify 3-7 major themes or arguments across all sources.
  • Track direct quotes with attribution (author, source title, page/section if available).
  • Note areas of agreement, tension, or contradiction between sources.
  • Distinguish claims from evidence — report what sources say, do not add unsupported conclusions.
  • When sources conflict, prepare to present both positions.

Step 3: Write briefing document

Follow this structure exactly:

# [Report Title]: Briefing Document

## Executive Summary

[2-3 paragraphs: the critical takeaways a busy reader needs. A reader
who reads only this section should understand the core findings.]

## [Theme 1 Name]

- [Key point with supporting evidence]
- "[Exact quote]" ([Source Author/Title])
- [Implication or significance]

## [Theme 2 Name]

[Continue for each major theme identified in Step 2]

## Points of Tension

[Where sources disagree or present competing views. Present both sides
without taking a position.]

## Conclusions and Implications

[Synthesis of what the evidence collectively suggests. Forward-looking
implications where supported by the sources.]

## Sources

1. [Author]. [Title]. [Date/Publication if available].

Step 4: Validate quality

Before finalizing, verify:
- [ ] Every claim traces to a specific source (no fabricated content)
- [ ] All major themes from sources are represented
- [ ] Direct quotes are exact and attributed
- [ ] Executive Summary stands alone as a complete overview
- [ ] Analysis is organized by theme, not by source
- [ ] Tone is objective throughout — no editorializing
- [ ] Markdown renders correctly (headings, lists, blockquotes)

Tone and voice

  • Objective and analytical — present findings, not opinions.
  • Incisive — cut to what matters, do not pad.
  • Use "The sources indicate..." or "According to [Author]..." not "I found..." or "We see..."
  • Prefer active voice. Avoid hedging unless uncertainty is genuine.
  • Match the depth of analysis to the complexity of the sources.

Context adjustments

  • Single source: deeper analysis, more granular themes, extended quotes.
  • Multiple sources: comparative analysis, synthesis across sources, highlight agreements and tensions.
  • Technical sources: preserve technical terminology, include code references where relevant.
  • Non-English sources: translate key quotes, note original language.

Anti-patterns

  • Summarizing each source sequentially instead of synthesizing by theme.
  • Burying the key finding in the middle of the document.
  • Including every detail instead of the most significant findings.
  • Editorializing beyond what sources support.
  • Writing an Executive Summary that requires reading the full document to understand.

Skill handoffs

WhenRun
After briefing is written, audit prose qualitydocs-writing
If briefing needs to become a presentationcreating-presentations

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.6%
按下载量换算54

Claude

32.59%
按下载量换算52

Cursor

19.64%
按下载量换算31

Gemini CLI

8.92%
按下载量换算14

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills