Skill: clarezoe/linuxdo-application (version 1.0.0)

--- name: linuxdo-application description: > Craft high-pass-rate, de-AI'd Chinese applications (小作文) for Linux.do registration. Conducts an adaptive survey to learn the applicant's real background, then generates natural, rule-compliant plain text ready to paste. All user interactions in Chinese. metadata: openclaw: emoji: "📝" homepage: "https://github.com/Fei2-Labs/skill-genie" version: "1.0.0" category: "content-generation" author: "Skill Genie" license: "MIT" language: backend: English user-facing: Chinese --- # Linux.do Application Writer Generate a natural, high-pass-rate registration application for Linux.do through an adaptive interview followed by rule-aware, de-AI'd text generation. ## Triggers - "write linux.do application" - "linux.do 小作文" - "linux.do 注册申请" - "help me apply to linux.do" ## Quick Reference | Input | Output | Duration | |-------|--------|----------| | Answers to 5-8 survey questions | Plain text Chinese application (~80-150 chars) | 5-10 min | ## Process ### Phase 1: Applicant Survey Conduct an adaptive interview in Chinese to collect the 4 required info blocks. Ask **one question at a time**. Adapt follow-ups based on answers. **Core questions (ask in Chinese, adapt order based on flow):** 1. 你平时主要做什么？（工作、学习、兴趣方向） 2. 你是怎么知道 Linux.do 的？（搜索、朋友推荐、看到某个帖子？） 3. 你在上面浏览过哪些内容？有没有印象深的帖子或话题？ 4. 为什么现在想注册？有什么具体的需求或场景吗？ 5. 注册之后你打算怎么用？（潜水、回帖、关注某类话题、分享经验？） **Adaptive rules:** - If an answer is vague (e.g., "想学习交流"), probe deeper: "具体想学什么？在哪看到过相关讨论？" - If an answer already covers multiple blocks, skip redundant questions - If the applicant mentions a specific post/topic, ask them to elaborate — this is gold - Stop when all 4 info blocks are covered (see references/linuxdo-rules.md) **Verification:** Before moving to Phase 2, confirm internally: - [ ] Background covered (what they do/follow) - [ ] Discovery path covered (how they found the site) - [ ] Join reason covered (why register now, specific scenario) - [ ] Usage plan covered (what they'll do with the account) If any block is missing, ask one more targeted question. ### Phase 2: Draft Generation + Risk Check Generate the application draft using collected info. **Generation rules:** 1. Write in first person, casual Chinese — like telling a friend why you signed up 2. Target 80-150 characters. Not too short (looks lazy), not too long (looks try-hard) 3. Weave all 4 info blocks naturally — do NOT use a 4-paragraph structure 4. Use the applicant's own words and phrasing where possible 5. No greetings, no sign-offs, no "你好" or "谢谢" — just the substance 6. Allow sentence fragments, colloquialisms, and imperfect grammar 7. Vary sentence length: mix short punchy lines with longer ones **Risk check — scan the draft against these (see references/linuxdo-rules.md):** | Risk Level | Check | |------------|-------| | HIGH | Does it mention background? Discovery path? Join reason? | | HIGH | Is there any concrete fact, or is it all fluff? | | HIGH | Does it look like a template that could apply to anyone? | | MEDIUM | Is it only admiration/flattery without substance? | | MEDIUM | Is it only "I can contribute X" without explaining why here? | | MEDIUM | Is info density too low for the character count? | If any HIGH risk is triggered, rewrite before proceeding. ### Phase 3: De-AI Polish + Final Output Run the draft through the full de-AI checklist (see references/de-ai-checklist.md). **Audit steps:** 1. Check all 12 AI markers — flag and rewrite any matches 2. Read the text as if you're a human reviewer — does it smell like AI? 3. Apply the 3-question smell test: - Could you swap details and reuse this for someone else? → too generic - Does every sentence add new information? → cut filler - Would you text this to a friend? → loosen if too formal **Output:** Present the final application as plain text in a code block. Tell the user in Chinese: "这是你的申请文，可以直接复制粘贴到注册页面。" If the user wants changes, revise and re-run Phase 3 checks. ## Anti-Patterns | Avoid | Why | Instead | |-------|-----|---------| | Parallel structures (我喜欢X，我热爱Y) | AI marker #1 | Vary grammar patterns | | 三段式 (首先/其次/最后) | AI marker #2 | Drop scaffolding | | AI vocab (赋能/深耕/沉淀/赛道) | AI marker #5 | Use plain spoken Chinese | | Flattery (久仰大名/慕名而来) | High-risk per rules | Replace with real discovery story | | Generic motivation (想学习交流) | Medium-risk per rules | State specific use case | | Press-release tone | AI marker #9 | Add 吧/嘛/其实/反正 | ## Verification After final output, confirm: - [ ] All 4 info blocks present - [ ] 80-150 characters - [ ] Zero high-risk patterns - [ ] Passes all 12 de-AI markers - [ ] Reads like a real person wrote it - [ ] Plain text, no formatting ## Extension Points 1. **Rule updates:** When Linux.do changes registration rules, update `references/linuxdo-rules.md` 2. **New AI markers:** As AI detection evolves, add markers to `references/de-ai-checklist.md` 3. **Multi-community:** Adapt the survey + rule framework for other invite-only communities ## References - [Linux.do Rules & Signals](references/linuxdo-rules.md) — official rules + community patterns - [De-AI Checklist](references/de-ai-checklist.md) — 12 AI markers to detect and fix ## Related Skills | Skill | Use When | |-------|----------| | wechat-compliance-check | Need to check Chinese content for platform compliance | | psychology-master | Need deeper user profiling during survey | | humanizer-zh | Additional de-AI processing for Chinese text |

path: README.md
content: # Linux.do Application Writer

Craft high-pass-rate, de-AI'd Chinese applications (小作文) for Linux.do registration through an adaptive survey and rule-aware text generation.

## Install

**OpenClaw / ClawHub:**
```bash
clawhub install linuxdo-application
```

**Manual:**
```bash
git clone https://github.com/Fei2-Labs/skill-genie.git
cp -r skill-genie/linuxdo-application ~/.openclaw/skills/linuxdo-application
```

## Usage

Trigger the skill with any of these phrases:
- "write linux.do application"
- "linux.do 小作文"
- "linux.do 注册申请"
- "help me apply to linux.do"

The agent will:
1. Conduct an adaptive Chinese-language survey (5-8 questions, one at a time)
2. Generate a draft application covering all 4 required info blocks
3. Run a risk check and de-AI polish pass before outputting plain text

## Compatibility

| Agent | Compatible |
|-------|-----------|
| OpenClaw | Yes |
| Hermes | Yes |
| Claude Code | Yes |
| Other SKILL.md agents | Yes |

No scripts or external dependencies — pure SKILL.md workflow.

## File Structure

```
linuxdo-application/
├── SKILL.md                          # Main workflow
├── README.md                         # This file
└── references/
    ├── linuxdo-rules.md              # Official rules + community signals
    └── de-ai-checklist.md            # 12 AI markers to detect and fix
```

## License

MIT


path: references/de-ai-checklist.md
content: # De-AI Checklist

12 markers that make Chinese text sound AI-generated. The agent must audit every draft
against these markers and rewrite any flagged sentences.

## Detection Markers

### Structural Markers

| # | Marker | Example | Fix |
|---|--------|---------|-----|
| 1 | **Parallel sentence structures** — 3+ sentences with identical grammar pattern | 我喜欢X，我热爱Y，我追求Z | Break the pattern; vary grammar |
| 2 | **Three-part formula (三段式)** — intro-body-conclusion with clear transitions | 首先...其次...最后 | Drop the scaffolding; just say it |
| 3 | **Uniform sentence length** — all sentences roughly the same character count | Every sentence 15-20 chars | Mix short (5-8) with medium (15-25) |
| 4 | **Bullet-point prose** — text reads like a formatted list without the bullets | Point 1. Point 2. Point 3. | Merge ideas into flowing text |

### Vocabulary Markers

| # | Marker | Example | Fix |
|---|--------|---------|-----|
| 5 | **AI cliché words** — 赋能、助力、深耕、沉淀、拥抱、赛道、底层逻辑、认知 | 深耕技术领域多年 | Use plain words: 做了好几年 |
| 6 | **Excessive connectives** — 此外、与此同时、不仅如此、值得一提的是 | 此外，我还关注了... | Drop the connector; start directly |
| 7 | **Grandiose metaphors** — 灯塔、宝藏、殿堂、星辰大海 | Linux.do 是技术人的灯塔 | Just say what it is plainly |
| 8 | **Negation-based emphasis** — 不是X而是Y pattern repeated | 不是简单的学习，而是深度的交流 | State it directly without the contrast |

### Tone Markers

| # | Marker | Example | Fix |
|---|--------|---------|-----|
| 9 | **Over-polished tone** — no colloquialisms, no casual markers | Reads like a press release | Add 吧、嘛、其实、反正、就是 |
| 10 | **Propaganda tone** — 共同进步、携手前行、共建生态 | 希望和大家共同进步 | Say what you'll actually do |
| 11 | **Perfect grammar throughout** — no fragments, no run-ons | Every sentence is grammatically flawless | Allow natural imperfections |
| 12 | **Flattery without substance** — 久仰大名、慕名而来、心向往之 | 久仰 Linux.do 大名 | Replace with how you actually found it |

## Audit Process

1. Read the draft sentence by sentence
2. Flag any sentence matching 1+ markers above
3. For each flagged sentence, rewrite using the "Fix" column guidance
4. Re-read the full text aloud — does it sound like someone talking, not writing an essay?
5. Final check: would a human reviewer think "this person actually wrote this"?

## Quick Smell Test

Ask these 3 questions about the final draft:
- **Could you swap the applicant's details and reuse this for someone else?** If yes → too generic, rewrite.
- **Does every sentence add new information?** If any sentence is pure filler → cut it.
- **Would you text this to a friend?** If it feels too formal → loosen the tone.


path: references/linuxdo-rules.md
content: # Linux.do Application Rules & Signals

Comprehensive rule set for crafting high-pass-rate Linux.do registration applications.
Sources: official announcements, FAQ, and public community experience posts.

## Hard Rules (Official — Pass/Fail)

### 1. Read FAQ/Guidelines First
Applicants must read the FAQ before registering. The registration page requires checking "已读".
Reviewers specifically flag applications that show the applicant didn't read the rules.

### 2. Self-Written Application
The application must be a ~50-character self-written text covering your background and why you want to join.
"Randomly filled" or "AI-generated" applications will not pass in principle.

### 3. Invited Users Are Also Reviewed
Even with an invitation link, the same application content is required and reviewed by admins.

### 4. Content Is Archived
Application content is not publicly displayed but is archived for future reference.
This means: don't treat it as throwaway text.

## Content Characteristics That Increase Pass Rate

### 1. Specificity > Enthusiasm
Easy-pass applications are concrete: what you tinker with, how you found Linux.do,
which topics you browsed, why you need an account, what you plan to participate in.
Facts + path + scenario = looks like a real person.

### 2. Site-Aligned Motivation
Generic phrases like "want to learn", "want to meet experts", "want to grow together"
carry zero information. Users report failing twice before rewriting with specific
site-related reasons and use cases.

### 3. Show You Know What the Site Is
If the application reveals you don't know what's discussed on Linux.do, or you treat it
as a generic "resource group / tech group / beginner site", pass rate drops.
This aligns with the official emphasis on "read the intro and rules first".

### 4. "How I'll Participate" Is a Bonus
Common pattern in successful applications: not just "I want to look around" but
"I've encountered similar problems", "I've seen solutions on the site",
"I want to reply, document, discuss X topic". This reads like a long-term user.

## Required Information Blocks (4 Blocks)

Every application should contain these 4 pieces:

| Block | What to Include |
|-------|----------------|
| **Real Background** | What you do, what fields you follow. Doesn't need to be complete. |
| **Discovery Path** | How you found Linux.do — search, friend, specific post, long-time lurker. |
| **Why Register Now** | Not abstract "want to join" but concrete: participate in X, reply to Y, follow Z. |
| **Account Usage Plan** | Read-only? Occasional replies? Follow specific topics? Be real and specific. |

## High-Risk Patterns (Likely Rejection)

| Pattern | Why It Fails |
|---------|-------------|
| No background/experience mentioned | Missing required info block |
| No explanation of how you found the site | Looks random |
| No reason for joining | Missing required info block |
| All fluff, no concrete facts | Template-like |
| Overly neat, uniform tone | Looks batch-generated |
| Clearly didn't read rules | Explicitly flagged by reviewers |

## Medium-Risk Patterns (Weak Signal)

| Pattern | Why It's Weak |
|---------|--------------|
| Only admiration/thanks/praise | Zero information density |
| Only listing your skills/contributions | Missing motivation |
| Only learning intent, no use case | Too vague |
| Barely over 50 chars, extremely low info density | Looks like minimum effort |

## Bonus Signals (Increase Pass Rate)

| Signal | Why It Helps |
|--------|-------------|
| Can describe how you encountered site content | Proves real exposure |
| Mentions real topics or participation plans | Shows genuine interest |
| Shows awareness of community rules and positioning | Aligned with official requirement |
| Natural, non-template expression | Passes the "human" smell test |

## Target Specs

- Length: 80-150 Chinese characters (sweet spot: enough detail, not rambling)
- Tone: casual, natural, like telling a friend why you signed up
- Language: Chinese (Simplified)
- Format: plain text, no markdown, no formatting


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)