Agent skill

技术科普文逻辑重构

将技术内容从信息堆砌型改写为逻辑递进型,按‘问题锚点→类比破冰→机制白描→前沿简述→避坑口诀→行动指引’六步结构组织,确保非技术读者能沿单一认知路径理解。

ECNU-ICALKgithub.com/ECNU-ICALKGitHub ↗
claude-code
Install
npx skills add ECNU-ICALK/AutoSkill --skill 技术科普文逻辑重构 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 1 KB
Bundled scripts: none
Version: 0.1.0
Path: SkillBank/Users/u6/技术科普文逻辑重构/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 539
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 技术科普文逻辑重构 将技术内容从信息堆砌型改写为逻辑递进型,按‘问题锚点→类比破冰→机制白描→前沿简述→避坑口诀→行动指引’六步结构组织,确保非技术读者能沿单一认知路径理解。 ## Prompt # Goal 重写技术科普类内容,使其逻辑清晰、主线唯一、无信息过载,适配大众读者(如微信公众号)的认知节奏。 # Constraints & Style - 严格采用六段式线性结构:① 用真实痛点开场(设备/成本/体验瓶颈);② 用生活化类比定义核心概念(禁用术语直译);③ 用‘机制白描’替代原理阐述(只说‘它怎么做’,不说‘为什么这么做’);④ 前沿进展仅列3个以内可感知效果(如‘跑得更快’‘省更多显存’‘能在Mac上跑’),不提方法名;⑤ 避坑建议必须转化为口语化口诀(如‘量化不是削足适履,而是量体裁衣’);⑥ 行动指引聚焦‘下一步做什么’,给出1–3个具体、可选、低门槛的工具/路径。 - 禁用任何形式的术语罗列、方法对比表格、参数指标堆砌、多级嵌套列表。 - 每段≤5行,段间空一行;关键句加emoji引导但不超过1个/段;全文不出现‘综上所述’‘值得注意的是’等过渡套话。 - 所有技术名词(如Q4_K_M、AWQ、NF4)首次出现时必须附带括号内一句话人话解释(例:‘Q4_K_M——llama.cpp里最稳的轻量模式’)。 # Workflow None ## Triggers - 内容太多太杂 - 逻辑不够清晰 - 重写成大众能懂的 - 去掉技术黑话 - 按认知路径组织

What's inside
Steps it walks through
  1. Prompt
  2. Triggers
More from AutoSkill
All skills →
About this skill
What does the 技术科普文逻辑重构 skill do?

将技术内容从信息堆砌型改写为逻辑递进型,按‘问题锚点→类比破冰→机制白描→前沿简述→避坑口诀→行动指引’六步结构组织,确保非技术读者能沿单一认知路径理解。

How do I install it?

Run `npx skills add ECNU-ICALK/AutoSkill --skill 技术科普文逻辑重构 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going