菜单
Write clear, engaging technical content from real experience. Use when writing blog posts, documentation, tutorials, or technical articles.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/proffesor-for-testing/sentinel-api-testing --skill technical-writing命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | technical-writing |
| description | Write clear, engaging technical content from real experience. Use when writing blog posts, documentation, tutorials, or technical articles. |
| category | communication |
| priority | medium |
| tokenEstimate | 800 |
| agents | ["qe-quality-analyzer","qe-api-contract-validator"] |
| implementation_status | optimized |
| optimization_version | 1 |
| last_optimized | 2025-12-03T00:00:00.000Z |
| dependencies | [] |
| quick_reference_card | true |
| tags | ["writing","documentation","communication","blogs","tutorials"] |
<default_to_action> When writing technical content:
Blog Post Structure:
# Title (specific promise)
## Opening (2-3 paragraphs)
- Hook: The problem or insight
- Context: Why this matters
- Promise: What they'll learn
## Body (3-5 sections)
- One clear idea per section
- Support with examples/code/data
## Closing
- Key takeaway (1-2 sentences)
- Action reader can take
Before/After: ❌ "We implemented a comprehensive testing strategy..." ✅ "We moved exploratory testing into sprint planning. QE now pairs with devs during story refinement." </default_to_action>
| Principle | Bad | Good |
|---|---|---|
| Lead with value | "In today's landscape..." | "Here's how we cut bugs 60%" |
| Show, don't tell | "We improved testing" | "Bug detection: 12→47 per sprint" |
| Be specific | "Performance improved" | "Response time: 2.3s→180ms" |
| Honest trade-offs | "This approach is best" | "TDD slowed velocity 20%, reduced bugs 75%" |
| Kill | Reason |
|---|---|
| basically, actually, probably | Hedge words |
| leverage, synergy, paradigm | Corporate speak |
| very, really, quite | Unnecessary qualifiers |
| it should be noted that | Just note it |
Before publishing:
Before: "We decided to implement a more comprehensive testing strategy that would allow us to catch bugs earlier in the development lifecycle."
After: "We moved exploratory testing into sprint planning. QE now pairs with devs during story refinement, identifying risks before code is written."
Before: "The benefits of this approach are numerous and include improved quality, faster feedback loops, and better team collaboration."
After: "Three outcomes: bugs found 2 days earlier on average, 30% fewer regression issues, and devs now ask QE for input during design."
// Generate documentation from code
const docs = await Task("Generate Docs", {
source: 'src/services/PaymentService.ts',
format: 'markdown',
includeExamples: true
}, "qe-quality-analyzer");
// Review documentation quality
const review = await Task("Review Docs", {
files: ['README.md', 'docs/api.md'],
checkClarity: true,
checkCodeExamples: true
}, "qe-quality-analyzer");
aqe/technical-writing/
├── generated-docs/* - Auto-generated documentation
├── reviews/* - Documentation review findings
└── templates/* - Reusable doc templates
const docsFleet = await FleetManager.coordinate({
strategy: 'documentation',
agents: [
'qe-quality-analyzer', // Generate and review
'qe-api-contract-validator' // API doc accuracy
],
topology: 'sequential'
});
You're not writing to impress. You're writing to help people solve problems you've already solved. Be the colleague you wish you'd had.
Write from experience. Only write about what you've done in production. If exploring, say so.
基于 SOC 职业分类