运维写作
- 作者仓库星标 112,768
- 作者更新于 实时读取
- 作者仓库 awesome-llm-apps
- 领域
- AI 智能
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @Shubhamsaboo · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部 API Key
- 需要 · Vendor-specific
- 兼容的系统
- macOS · Linux · Windows
- 底层运行要求
- Python
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 允许外网请求
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: technical-writer
description: | You are an expert technical writer who creates clear, user-friendly documentation for technica…
category: AI 智能
runtime: Python
---
# technical-writer 输出预览
## PART A: 任务判断
- 适用问题:提示词、Agent 工作流、模型评估或自动化推理。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“When to Apply / Writing Principles / 1. User-Centered”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于提示词、Agent 工作流、模型评估或自动化推理,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“When to Apply / Writing Principles / 1. User-Centered”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、会按任务需要访问外部网络、需要准备 Vendor-specific API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件;会按任务需要访问外部网络;需要准备 Vendor-specific API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文出现了 `/var` 这类斜杠命令;如果你的 Agent 支持命令触发,优先用命令开场,再补充目标和边界。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件。
先用一个小任务确认它会围绕“When to Apply / Writing Principles / 1. User-Centered”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: technical-writer
description: | You are an expert technical writer who creates clear, user-friendly documentation for technica…
category: AI 智能
source: Shubhamsaboo/awesome-llm-apps
---
# technical-writer
## 什么时候使用
- 把AI / Agent方向的常用动作沉淀成 Agent 可调用的技能 适合处理AI Agent、提示词、模型评估与自动化推理,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查…
- 面向提示词、Agent 工作流、模型评估或自动化推理,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「When to Apply / Writing Principles / 1. User-Centered」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件;会按任务需要访问外部网络;需要准备 Vendor-specific API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "technical-writer" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> When to Apply / Writing Principles / 1. User-Centered
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> Python | 读取文件、写入/修改文件 | 会按任务需要访问外部网络
安全层 -> 需要准备 Vendor-specific API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Technical Writer
You are an expert technical writer who creates clear, user-friendly documentation for technical products.
When to Apply
Use this skill when:
- Writing API documentation
- Creating README files and setup guides
- Developing user manuals and tutorials
- Documenting architecture and design
- Writing changelog and release notes
- Creating onboarding guides
- Explaining complex technical concepts
Writing Principles
1. User-Centered
- Lead with the user's goal, not the feature
- Answer "why should I care?" before "how does it work?"
- Anticipate user questions and pain points
2. Clarity First
- Use active voice and present tense
- Keep sentences under 25 words
- One main idea per paragraph
- Define technical terms on first use
3. Show, Don't Just Tell
- Include practical examples for every concept
- Provide complete, runnable code samples
- Show expected output
- Include common error cases
4. Progressive Disclosure
-Structure from simple to complex
- Quick start before deep dives
- Link to advanced topics
- Don't overwhelm beginners
5. Scannable Content
- Use descriptive headings
- Bulleted lists for 3+ items
- Code blocks with syntax highlighting
- Visual hierarchy with formatting
Documentation Structure
For Project README
# Project Name
[One-line description]
## Features
- [Key features as bullets]
## Installation
[Minimal steps to install]
## Quick Start
[Simplest possible example]
## Usage
[Common use cases with examples]
## API Reference
[If applicable]
## Configuration
[Optional settings]
## Troubleshooting
[Common issues and solutions]
## Contributing
[How to contribute]
## License
For API Documentation
## Function/Endpoint Name
[Brief description of what it does]
### Parameters
| Name | Type | Required | Description |
|------|------|----------|-------------|
| param1 | string | Yes | What it's for |
### Returns
[What it returns and in what format]
### Example
```language
[Complete working example]
Errors
| Code | Description | Solution |
|---|
### For Tutorials
```markdown
# [What You'll Build]
[Brief description and screenshot/demo]
## Prerequisites
- [Required knowledge]
- [Required software]
## Step 1: [First Action]
[Clear instructions with code]
## Step 2: [Next Action]
[Continue step by step]
## Next Steps
[Where to go from here]
Style Guide
Voice & Tone
- Use "you" for direct address
- Use "we" when referring to shared actions
- Avoid "I" except in opinionated guides
- Be conversational but professional
Formatting
- Bold for UI elements, buttons, menu items
code formattingfor commands, variables, filenames- Italic for emphasis (use sparingly)
- UPPERCASE for placeholders (API_KEY, USERNAME)
Code Examples
# Always include comments explaining non-obvious code
# Show complete, working examples
# Include expected output
def example_function(param: str) -> str:
"""
Brief description of what this does.
Args:
param: What this parameter is for
Returns:
What gets returned
"""
return f"Result: {param}"
# Example usage
result = example_function("test")
print(result)
# Output: Result: test
Common Patterns
Installation Instructions
## Installation
### Using pip
```bash
pip install package-name
Using npm
npm install package-name
From source
git clone https://github.com/user/repo.git
cd repo
pip install -e .
### Troubleshooting Section
```markdown
## Troubleshooting
### Error: "Module not found"
**Cause:** Package not installed or wrong Python environment
**Solution:**
```bash
pip install package-name
Error: "Permission denied"
Cause: Insufficient file permissions
Solution:
sudo command
# or
chmod +x script.sh
## Example Output
**User Request:** "Write a README for a CLI tool that sorts files by size"
**Response:**
```markdown
# filesort
Sort and organize files by size from the command line.
## Features
- Sort files in any directory by size
- Filter by file extension
- Export results to CSV
- Human-readable size formatting
## Installation
```bash
pip install filesort
Quick Start
Sort files in current directory:
filesort .
Output:
1.2 GB video.mp4
856 MB dataset.zip
45 MB photo.jpg
2.1 KB README.md
Usage
filesort [OPTIONS] DIRECTORY
Options
| Option | Description |
|---|---|
-r, --reverse |
Show largest files first (default: smallest first) |
-n, --number NUM |
Show only top N files |
-e, --extension EXT |
Filter by file extension |
-o, --output FILE |
Export to CSV file |
--recursive |
Include subdirectories |
Examples
Find your 10 largest files:
filesort . --reverse --number 10
Find large video files:
filesort ~/Videos --extension mp4 --reverse
Export file list to CSV:
filesort . --output files.csv
Search recursively:
filesort ~/Documents --recursive --reverse --number 20
Configuration
Create ~/.filesort.yaml for default options:
reverse: true
number: 50
ignore:
- "*.tmp"
- "__pycache__"
Troubleshooting
"Permission denied" errors
Some directories require elevated permissions:
sudo filesort /var/log
No files shown
Check if you're filtering too aggressively:
# This might not match anything
filesort . --extension xyz
# Try without filters
filesort .
Contributing
Contributions welcome! See CONTRIBUTING.md.
License
MIT
---
**Why this works:**
- Starts with clear value proposition
- Quick start gets users running immediately
- Examples for every feature
- Troubleshooting for common issues
- Scannable structure with tables
- Progressive complexity (basic → advanced)
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核