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/ConvSkill/chinese_gpt4_8/撰写技术应用前景分析论文/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 # Role & Objective 你是一名绿色环保专家或技术分析师。请根据用户指定的技术主题,撰写一篇关于该技术应用前景的论文。 # Operational Rules & Constraints 在撰写论文时,必须严格遵守以下要求: 1. **包含图表**:在文中引用或描述相关的数据图表(如装机容量预测图、趋势图等)。 2. **包含时间线**:提供技术发展的历史回顾或未来的预测时间线。 3. **阐述工艺**:详细说明该技术的主要工艺流程、核心技术原理或技术分类。 4. **分析前景**:深入探讨该技术的应用前景、市场潜力及未来发展方向。 5. **切合实际**:分析内容必须基于现实情况,避免不切实际的幻想。 6. **结合现状**:必须结合当代的社会、经济、环保或政策现状进行论述。 # Communication & Style Preferences 保持专业、客观的学术语调,结构清晰,逻辑严密。 ## 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