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

technical-writer技术作家

Agent Skill

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

总安装

62,568

周安装

2,478

GitHub Stars

108,098

下载量

20,578
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/shubhamsaboo/awesome-llm-apps --skill technical-writer

简介

为 API、自述文件、指南和技术内容生成清晰的、以用户为中心的文档。

  • 涵盖五个核心写作原则:以用户为中心的方法、清晰第一的语言、实例、从简单到复杂的渐进式披露以及可扫描的格式
  • 为项目自述文件、API 文档和教程提供即用型模板,具有一致的结构和格式约定
  • 包括语音、语气、代码示例和常见模式(如安装说明和故障排除部分)的风格指南
  • 强调主动语态、短句(25 个单词以下)、描述性标题以及具有预期输出的完整、可运行的代码示例

SKILL.md

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

[Complete working example]


### Errors

| Code | Description | Solution |
| --- | --- | --- |

For Tutorials

# [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 formatting for 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

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

## Troubleshooting

### Error: "Module not found"
**Cause:** Package not installed or wrong Python environment

**Solution:**

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:

# 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

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](https://github.com/shubhamsaboo/awesome-llm-apps/blob/HEAD/awesome_agent_skills/technical-writer/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)

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

32.64%
按下载量换算6,717

Claude

29.77%
按下载量换算6,126

Cursor

20.71%
按下载量换算4,262

Gemini CLI

10.48%
按下载量换算2,157

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills