explainx.ainewsletter3.4k
Productivity

chinese-output▌

lostabaddon/headlessknight · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/lostabaddon/headlessknight --skill chinese-output
0 commentsdiscussion
summary

中文句子中使用的标点符号必须是全角标点，包括以下这些标点：

skill.md
  1. 输出包含任何中文字符（汉字、中文标点）
  2. 需要使用中文标点符号
  3. 回复用中文提问的用户
  4. 中英文混排内容

中文句子中使用的标点符号必须是全角标点，包括以下这些标点：

，。；：‘’“”《》？！、～（）【】「」——……

尤其注意：

  • 中文后的逗号必须是全角逗号，而不能是半角逗号,
  • 中文后的句号必须是全角句号。而不能是半角句号.
  • 中文后的问号必须是全角问号？而不能是半角问号?
  • 中文后的惊叹号必须是全角惊叹号！而不能是半角惊叹号!
  • 中文后的冒号必须是全角冒号：而不能是半角冒号:，尤其在一段文字的最后时
  • 中文后的分号必须是全角分号；而不能是半角分号;
  • 中文后的波浪号必须是全角波浪号～而不能是半角波浪号~
  • 中文后的顿号必须是全角顿号、而不能是半角逗号,
  • 中文后的破折号必须是两个一组的全角破折号——而不能是半角破折号----
  • 中文后的省略号必须是两个一组的全角省略号……而不能是半角省略号...
  • 中文为主的内容的前后用的双引号必须是全角双引号“和”，而不能是半角双引号"，比如 “数学节是什么样的节日？”
  • 中文为主的内容的前后用的单引号必须是全角单引号‘和’，而不能是半角单引号'，比如 夏洛克说：“这个‘复仇’是德语。”
  • 中文为主的内容的前后用的书名号必须是全角书名号《和》，而不能是半角书名号<和>，比如 《永乐大典》
  • 中文为主的内容的前后用的圆括号必须是全角圆括号（和），而不能是半角圆括号(和)，比如 （才没有呢！）
  • 中文为主的内容的前后用的方括号必须是全角方括号【和】，而不能是半角方括号[和]，比如 【大家好】
  • 中文为主的内容的前后用的花括号必须是全角花括号「和」，而不能是半角花括号{和}，比如 「康熙字典」

如果中文与非中文混合，则使用中文符号的标准为：

  • 如果是非成套标点符号（比如逗号、句号等），则出现在中文字符后，使用中文标点；出现在非中文字符后，则根据该字符所属语言绝对使用什么标点
  • 如果是成套标点符号（比如单引号、双引号、书名号、括号等），则如果这部分内容的第一个非空字符或者最后一个非空字符是中文，则使用中文标点符号

其他注意事项：

  • 中文标点符号与非中文标点符号之间要使用一个半角空格来做区隔
  • 需要自行判断其他情况下使用中文标点符号还是非中文标点符号，务必保持上下文一致性，但又要和文档本身的规定吻合（比如代码中就不能乱使用中文标点）
  • shell 脚本、Javascript 脚本、Python 脚本等脚本或命令行指令中不要使用本技能
how to use chinese-output

How to use chinese-output on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • ›Cursor installed and configured on your development machine
  • ›Node.js version 16.0+ with npm package manager (verify with node --version)
  • ›Active project directory or workspace where you want to add chinese-output
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/lostabaddon/headlessknight --skill chinese-output

The skills CLI fetches chinese-output from GitHub repository lostabaddon/headlessknight and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/chinese-output

Reload or restart Cursor to activate chinese-output. Access the skill through slash commands (e.g., /chinese-output) or your agent's skill management interface.

⚠

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases▌

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

✓

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

✓

Save 3-5 hours/week on communication overhead

Implementation Guide▌

Prerequisites

  • ›Claude Desktop or compatible AI client
  • ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • ›Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • ⚠Not validating competitive research—verify facts before sharing
  • ⚠Accepting user stories without involving engineering team
  • ⚠Over-relying on frameworks without qualitative judgment
  • ⚠Not customizing outputs to company culture and communication style
  • ⚠Skipping stakeholder validation of generated requirements

Best Practices▌

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • −Don't publish competitive analysis without fact-checking
  • −Don't finalize user stories without engineering review
  • −Don't make prioritization decisions solely on AI scoring
  • −Don't skip customer validation of generated requirements
  • −Don't ignore company-specific context and culture

💡 Pro Tips

  • ★Provide context: company goals, constraints, customer feedback
  • ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • ★Use skill for 70% generation + 30% customization to company needs

When to Use This▌

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path▌

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.7★★★★★39 reviews
  • ★★★★★Yusuf Choi· Dec 28, 2024

    chinese-output has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Dhruvi Jain· Dec 20, 2024

    chinese-output fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • ★★★★★Michael Choi· Dec 16, 2024

    We added chinese-output from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Li Agarwal· Dec 4, 2024

    Registry listing for chinese-output matched our evaluation — installs cleanly and behaves as described in the markdown.

  • ★★★★★Mateo Yang· Nov 23, 2024

    chinese-output fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • ★★★★★Oshnikdeep· Nov 11, 2024

    Registry listing for chinese-output matched our evaluation — installs cleanly and behaves as described in the markdown.

  • ★★★★★Nia Khanna· Nov 7, 2024

    chinese-output reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • ★★★★★Nia Patel· Oct 26, 2024

    Registry listing for chinese-output matched our evaluation — installs cleanly and behaves as described in the markdown.

  • ★★★★★Nia Malhotra· Oct 14, 2024

    We added chinese-output from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Ganesh Mohane· Oct 2, 2024

    chinese-output reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 39

1 / 4