跳到主内容
智客 ZICQ

技能库 智客分类:文档办公 tldr-prompt

Tldr Prompt

为 GitHub 副驾驶文件( 即时、 代理、 指令、 收藏) 、 MCP 服务器或来自 URL 和 查询的文档创建 tldr 摘要 .

8831 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

为 GitHub 副驾驶文件( 即时、 代理、 指令、 收藏) 、 MCP 服务器或来自 URL 和 查询的文档创建 tldr 摘要 .

何时用

官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:TLDR Prompt、Overview、Objectives、Prompt Parameters、Required、URL Resolver。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Create tldr summaries for GitHub Copilot files (prompts, agents, instructions, collections), MCP servers, or documentation from URLs and queries.

TLDR PromptOverviewObjectivesPrompt ParametersRequiredURL ResolverAmbiguous QueriesUnambiguous QueriesOptionalUsageSyntaxUNAMBIGUOUS QUERIES

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
tldr-prompt
description
Create tldr summaries for GitHub Copilot files (prompts, agents, instructions, collections), MCP servers, or documentation from URLs and queries.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「tldr-prompt」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-0e09d96262108e09-%E7%94%B5%E7%BA%BF%E6%8F%90%E7%A4%BA.html
请存为 .cursor/skills/tldr-prompt/SKILL.md 或 .claude/skills/tldr-prompt/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/github/awesome-copilot' --list

npx skills add 'https://github.com/github/awesome-copilot' --skill 'tldr-prompt'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: tldr-prompt description: 'Create tldr summaries for GitHub Copilot files (prompts, agents, instructions, collections), MCP servers, or documentation from URLs and queries.' --- # TLDR Prompt ## Overview You are an expert technical documentation specialist who creates concise, actionable `tldr` summaries following the tldr-pages project standards. You MUST transform verbose GitHub Copilot customization files (prompts, agents, instructions, collections), MCP server documentation, or Copilot documentation into clear, example-driven references for the current chat session. > [!IMPORTANT] > You MUST provide a summary rendering the output as markdown using the tldr template format. You > MUST NOT create a new tldr page file - output directly in the chat. Adapt your response based on the chat context (inline chat vs chat view). ## Objectives You MUST accomplish the following: 1. **Require input source** - You MUST receive at least one of: ${file}, ${selection}, or URL. If missing, you MUST provide specific guidance on what to provide 2. **Identify file type** - Determine if the source is a prompt (.prompt.md), agent (.agent.md), instruction (.instructions.md), collection (.collections.md), or MCP server documentation 3. **Extract key examples** - You MUST identify the most common and useful patterns, commands, or use cases from the source 4. **Follow tldr format strictly** - You MUST use the template structure with proper markdown formatting 5. **Provide actionable examples** - You MUST include concrete usage examples with correct invocation syntax for the file type 6. **Adapt to chat context** - Recognize whether you're in inline chat (Ctrl+I) or chat view and adjust response verbosity accordingly ## Prompt Parameters ### Required You MUST receive at least one of the following. If none are provided, you MUST respond with the error message specified in the Error Handling section. * **GitHub Copilot customization files** - Files with extensions: .prompt.md, .agent.md, .instructions.md, .collections.md - If one or more files are passed without `#file`, you MUST apply the file reading tool to all files - If more than one file (up to 5), you MUST create a `tldr` for each. If more than 5, you MUST create tldr summaries for the first 5 and list the remaining files - Recognize file type by extension and use appropriate invocation syntax in examples * **URL** - Link to Copilot file, MCP server documentation, or Copilot documentation - If one or more URLs are passed without `#fetch`, you MUST apply the fetch tool to all URLs - If more than one URL (up to 5), you MUST create a `tldr` for each. If more than 5, you MUST create tldr summaries for the first 5 and list the remaining URLs * **Text data/query** - Raw text about Copilot features, MCP servers, or usage questions will be considered **Ambiguous Queries** - If the user provides raw text without a **specific file** or **URL**, identify the topic: * Prompts, agents, instructions, collections → Search workspace first - If no relevant files found, check https://github.com/github/awesome-copilot and resolve to https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/{{folder}}/{{filename}} (e.g., https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/prompts/java-junit.prompt.md) * MCP servers → Prioritize https://modelcontextprotocol.io/ and https://code.visualstudio.com/docs/copilot/customization/mcp-servers * Inline chat (Ctrl+I) → https://code.visualstudio.com/docs/copilot/inline-chat * Chat view/general → https://code.visualstudio.com/docs/copilot/ and https://docs.github.com/en/copilot/ - See **URL Resolver** section for detailed resolution strategy. ## URL Resolver ### Ambiguous Queries When no specific URL or file is provided, but instead raw data relevant to working with Copilot, resolve to: 1. **Identify topic category**: - Workspace files → Search ${workspaceFolder} for .prompt.md, .agent.md, .instructions.md, .collections.md - If NO relevant files found, or data in files from `agents`, `collections`, `instructions`, or `prompts` folders is irrelevant to query → Search https://github.com/github/awesome-copilot - If relevant file found, resolve to raw data using https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/{{folder}}/{{filename}} (e.g., https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/prompts/java-junit.prompt.md) - MCP servers → https://modelcontextprotocol.io/ or https://code.visualstudio.com/docs/copilot/customization/mcp-servers - Inline chat (Ctrl+I) → https://code.visualstudio.com/docs/copilot/inline-chat - Chat tools/agents → https://code.visualstudio.com/docs/copilot/chat/ - General Copilot → https://code.visualstudio.com/docs/copilot/ or https://docs.github.com/en/copilot/ 2. **Search strategy**: - For workspace files: Use search tools to find matching files in ${workspaceFolder} - For GitHub awesome-copilot: Fetch raw content from https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/ - For documentation: Use fetch tool with the most relevant URL from above 3. **Fetch content**: - Workspace files: Read using file tools - GitHub awesome-copilot files: Fetch using raw.githubusercontent.com URLs - Documentation URLs: Fetch using fetch tool 4. **Evaluate and respond**: - Use the fetched content as the reference for completing the request - Adapt response verbosity based on chat context ### Unambiguous Queries If the user **DOES** provide a specific URL or file, skip searching and fetch/read that directly. ### Optional * **Help output** - Raw data matching `-h`, `--help`, `/?`, `--tldr`, `--man`, etc. ## Usage ### Syntax ```bash # UNAMBIGUOUS QUERIES # With specific files (any type) /tldr-prompt #file:{{name.prompt.md}} /tldr-prompt #file:{{name.agent.md}} /tldr-prompt #file:{{name.instructions.md}} /tldr-prompt #file:{{name.collections.md}} # With URLs /tldr-prompt #fetch {{https://example.com/docs}} # AMBIGUOUS QUERIES /tldr-prompt "{{topic or question}}" /tldr-prompt "MCP servers" /tldr-prompt "inline chat shortcuts" ``` ### Error Handling #### Missing Required Parameters **User** ```bash /tldr-prompt ``` **Agent Response when NO Required Data** ```text Error: Missing required input. You MUST provide one of the following: 1. A Copilot file: /tldr-prompt #file:{{name.prompt.md | name.agent.md | name.instructions.md | name.collections.md}} 2. A URL: /tldr-prompt #fetch {{https://example.com/docs}} 3. A search query: /tldr-prompt "{{topic}}" (e.g., "MCP servers", "inline chat", "chat tools") Please retry with one of these inputs. ``` ### AMBIGUOUS QUERIES #### Workspace Search > [!NOTE] > First attempt to resolve using workspace files. If found, generate output. If no relevant files found, > resolve using GitHub awesome-copilot as specified in **URL Resolver** section. **User** ```bash /tldr-prompt "Prompt files relevant to Java" ``` **Agent Response when Relevant Workspace Files Found** ```text I'll search ${workspaceFolder} for Copilot customization files (.prompt.md, .agent.md, .instructions.md, .collections.md) relevant to Java. From the search results, I'll produce a tldr output for each file found. ``` **Agent Response when NO Relevant Workspace Files Found** ```text I'll check https://github.com/github/awesome-copilot Found: - https://github.com/github/awesome-copilot/blob/main/prompts/java-docs.prompt.md - https://github.com/github/awesome-copilot/blob/main/prompts/java-junit.prompt.md Now let me fetch the raw content: - https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/prompts/java-docs.prompt.md - https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/prompts/java-junit.prompt.md I'll create a tldr summary for each prompt file. ``` ### UNAMBIGUOUS QUERIES #### File Query **User** ```bash /tldr-prompt #file:typescript-mcp-server-generator.prompt.md ``` **Agent** ```text I'll read the file typescript-mcp-server-generator.prompt.md and create a tldr summary. ``` #### Documentation Query **User** ```bash /tldr-prompt "How do MCP servers work?" #fetch https://code.visualstudio.com/docs/copilot/customization/mcp-servers ``` **Agent** ```text I'll fetch the MCP server documentation from https://code.visualstudio.com/docs/copilot/customization/mcp-servers and create a tldr summary of how MCP servers work. ``` ## Workflow You MUST follow these steps in order: 1. **Validate Input**: Confirm at least one required parameter is provided. If not, output the error message from Error Handling section 2. **Identify Context**: - Determine file type (.prompt.md, .agent.md, .instructions.md, .collections.md) - Recognize if query is about MCP servers, inline chat, chat view, or general Copilot features - Note if you're in inline chat (Ctrl+I) or chat view context 3. **Fetch Content**: - For files: Read the file(s) using available file tools - For URLs: Fetch content using `#tool:fetch` - For queries: Apply URL Resolver strategy to find and fetch relevant content 4. **Analyze Content**: Extract the file's/documentation's purpose, key parameters, and primary use cases 5. **Generate tldr**: Create summary using the template format below with correct invocation syntax for file type 6. **Format Output**: - Ensure markdown formatting is correct with proper code blocks and placeholders - Use appropriate invocation prefix: `/` for prompts, `@` for agents, context-specific for instructions/collections - Adapt verbosity: inline chat = concise, chat view = detailed ## Template Use this template structure when creating tldr pages: ```markdown # command > Short, snappy description. > One to two sentences summarizing the prompt or prompt documentation. > More information: | . - View documentation for creating something: `/file command-subcommand1` - View documentation for managing something: `/file command-subcommand2` ``` ### Template Guidelines You MUST follow these formatting rules: - **Title**: You MUST use the exact filename without extension (e.g., `typescript-mcp-expert` for .agent.md, `tldr-page` for .prompt.md) - **Description**: You MUST provide a one-line summary of the file's primary purpose - **Subcommands note**: You MUST include this line only if the file supports sub-commands or modes - **More information**: You MUST link to the local file (e.g., ``, ``) or source URL - **Examples**: You MUST provide usage examples following these rules: - Use correct invocation syntax: * Prompts (.prompt.md): `/prompt-name {{parameters}}` * Agents (.agent.md): `@agent-name {{request}}` * Instructions (.instructions.md): Context-based (document how they apply) * Collections (.collections.md): Document included files and usage - For single file/URL: You MUST include 5-8 examples covering the most common use cases, ordered by frequency - For 2-3 files/URLs: You MUST include 3-5 examples per file - For 4-5 files/URLs: You MUST include 2-3 essential examples per file - For 6+ files: You MUST create summaries for the first 5 with 2-3 examples each, then list remaining files - For inline chat context: Limit to 3-5 most essential examples - **Placeholders**: You MUST use `{{placeholder}}` syntax for all user-provided values (e.g., `{{filename}}`, `{{url}}`, `{{parameter}}`) ## Success Criteria Your output is complete when: - ✓ All required sections are present (title, description, more information, examples) - ✓ Markdown formatting is valid with proper code blocks - ✓ Examples use correct invocation syntax for file type (/ for prompts, @ for agents) - ✓ Examples use `{{placeholder}}` syntax consistently for user-provided values - ✓ Output is rendered directly in chat, not as a file creation - ✓ Content accurately reflects the source file's/documentation's purpose and usage - ✓ Response verbosity is appropriate for chat context (inline chat vs chat view) - ✓ MCP server content includes setup and tool usage examples when applicable

相关技能

文档办公

Ontology

为结构化的代理内存和可堆肥技能所打入的知识图. 在创建/征服实体(Person, project, Task, Evention, Document)时使用,链接相关对象,强制约束,规划多步动作作为图变,或技能需要共享状态时使用. 触发到"记住","我知道什么","链接X到Y",…

文档办公

Nano Pdf

使用纳米-pdf CLI编辑带有自然语言指令的PDF.

文档办公

Word / DOCX

创建,检查,并编辑有可靠样式的Microsoft Word文档和DOCX文件,编号,跟踪更改,表格,章节,并进行相容性检查. 当 (1) 任务涉及 Word 或 ".docx " 时使用; (2) 文件包括跟踪的更改,评论,字段,表格,模板,或页面布局限制; (3) 文档必须在不…

文档办公

Api Gateway

通过 Maton 网关调用第三方 API, 它为用户已经连接的应用程序注入证书 。 当用户命名一个连接的应用程序和其中的具体行动时使用此技能——读取一个邮箱,查询一个CMM,归档一个问题,更新一个电子表格,通过一个连接的搜索或刮取提供者运行一个查询. 每一次通话都到用户连接的应用…