tech-blog-wrtting

撰写具有特定格式的技术博客文章。当用户要求撰写关于技术主题的博客文章或教程时使用。

Security Scan

The skill's instructions and requirements are coherent with its stated purpose (writing technical blog posts); it is instruction-only and requests no credentials, but it will create .md files in the current project directory which you should be aware of.

Purpose & Capability

Name/description: write technical blog posts. Declared requirements: none. The SKILL.md contains writing and formatting rules and a directive to save the output as a .md file — all consistent with the stated purpose.

Instruction Scope

Instructions stay focused on content and formatting. They explicitly instruct the agent to save the generated blog post as '<topic>.md' in the current project directory. That is within scope for a writing skill but implies file-system writes and potential overwrites; also the rule 'code examples must be runnable' is ambiguous (it does not explicitly tell the agent to execute code, but could lead to attempts to validate samples).

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing will be downloaded or written at install time.

Credentials

No environment variables, credentials, or external config paths are requested. The only operational effect is writing output files to the current project directory, which is proportional to the skill's purpose.

Persistence & Privilege

The skill is not always-enabled and does not request elevated privileges, but it does persistently write files to the agent's current project directory when invoked. Ensure the target workspace is appropriate to avoid overwriting important files.

Assessment

This skill appears to do what it says: generate formatted technical blog posts. Before installing or invoking it, decide whether you want the agent to write files into your current project directory (it will save <topic>.md), and avoid running it in directories containing sensitive or important files to prevent accidental overwrites. If you don't want the agent to create files automatically, instruct it explicitly (for example: 'produce the markdown in the response but do not write any files'). If you are concerned about 'runnable' code samples, ask the agent not to execute or validate samples, or to mark them as untested examples.

技术博客写作

工作流程

1. 明确写作内容
2. 参考写作规范进行内容创作

写作规范

内容结构

1. 标题：简洁有力，包含核心关键词
2. 开头：用反直觉的观点或问题抓住读者，不要用「首先让我们来了解...」这种无聊开头
3. 正文：
   • 每个段落不超过 5 句话
   • 专业术语首次出现时解释
   • 代码示例必须可运行
4. 结尾：总结要点 + 下一步行动建议

格式规范

• 使用 Markdown 格式
• 代码块要标注语言
• 重要观点用粗体强调

输出位置

将写作完成的博客文章以.md格式保存在当前项目文件下，文件命名为：<具体的写作主题>.md