JavaScript Concept Fact Checker
leonardomso/33-js-concepts
Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.
Draft, rewrite, or audit Chinese CSDN-style technical articles using a specific long-form teaching structure: a plain-text overall title, Markdown headings for section levels, dense natural…
Install Csdn Technical Writing
The automated check flagged lines worth reading first. See the safety section below.
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill csdn-technical-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills csdn-technical-writing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/csdn-technical-writing .claude/skills/csdn-technical-writing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "csdn-technical-writing" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/csdn-technical-writing into .claude/skills/csdn-technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "csdn-technical-writing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/csdn-technical-writingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill csdn-technical-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills csdn-technical-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/csdn-technical-writing .agents/skills/csdn-technical-writing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "csdn-technical-writing" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/csdn-technical-writing into .agents/skills/csdn-technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "csdn-technical-writing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill csdn-technical-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills csdn-technical-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/csdn-technical-writing .cursor/skills/csdn-technical-writing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "csdn-technical-writing" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/csdn-technical-writing into .cursor/skills/csdn-technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "csdn-technical-writing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FAIRY123456789/human-edge-agent-skills.git --path skills/csdn-technical-writing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill csdn-technical-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills csdn-technical-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/csdn-technical-writing .gemini/skills/csdn-technical-writing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "csdn-technical-writing" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/csdn-technical-writing into .gemini/skills/csdn-technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "csdn-technical-writing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FAIRY123456789/human-edge-agent-skills csdn-technical-writingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill csdn-technical-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/csdn-technical-writing .github/skills/csdn-technical-writing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "csdn-technical-writing" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/csdn-technical-writing into .github/skills/csdn-technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "csdn-technical-writing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill csdn-technical-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills csdn-technical-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/csdn-technical-writing .opencode/skills/csdn-technical-writing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "csdn-technical-writing" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/csdn-technical-writing into .opencode/skills/csdn-technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "csdn-technical-writing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
csdn-technical-writing- GitHub stars
- 103
- Token cost
- ~1.3k tokens
- SKILL.md length
- 597 words
- Files
- 3 (incl. scripts)
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- MIT
At a glance
Draft, rewrite, or audit Chinese CSDN-style technical articles using a specific long-form teaching structure: a plain-text overall title, Markdown headings for section levels, dense natural…
- Works in 8 steps: The article's overall title is plain… → First-level sections use #. → Second-level sections use ##. → …
- Technical tutorials
- SKILL.md covers Formatting contract, Private-project anonymization…, Teaching sequence and Paragraph style, plus 1 more section
- Runs Python scripts from its folder
What it does
Csdn Technical Writing is an agent skill from FAIRY123456789/human-edge-agent-skills. Draft, rewrite, or audit Chinese CSDN-style technical articles using a specific long-form teaching structure: a plain-text overall title, Markdown headings for section levels, dense natural paragraphs, beginner-first progression, commented code examples, and splitting when an article becomes too long. Use for technical tutorials, AI and backend articles, engineering practice notes, and beginner-friendly series.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `README.md` and `scripts/lint_csdn_article.py`).
It sits in Writing & Content, covering Technical writing. The repository describes itself as: 18 portable Agent Skills for voice-native AI, human judgment, microbets, social tact, writing, life systems, and safe deployment. The licence is MIT.
When your agent uses it
- Technical tutorials
- AI and backend articles
- Engineering practice notes
- Beginner-friendly series
Example prompts
- “/csdn-technical-writing”
Requirements
- Python 3
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- The article's overall title is plain text, not a Markdown heading.
- First-level sections use #.
- Second-level sections use ##.
- Prefer roughly 4–7 first-level sections for a normal article.
- Use full natural paragraphs. Do not split every sentence into a separate paragraph.
- Code goes in fenced code blocks.
- Default to approximately 1,500–2,000 Chinese characters per article, with a 3,000-character maximum unless the user explicitly requests a…
- Preserve enough details, working mechanisms, and short commands for a reader to reproduce the core technique. Cut repetition and generic…
What it can do on your machine
Read from SKILL.md and the folder at commit 31a0a16. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Csdn Technical Writing loads about 1.3k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 597 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: warnings
The automated check found patterns that need a careful read before installing.
- WarningTells the agent its actions are pre-authorized / not to stop for confirmationSKILL.md:42
hose details**. If in doubt, generalize without asking the user for private information. Verify titles, prose, tables, c
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from FAIRY123456789/human-edge-agent-skills at commit 31a0a16, republished under its MIT licence (© FAIRY123456789). 597 words, ~1,275 tokens.
Download SKILL.mdSave it as
.claude/skills/csdn-technical-writing/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- csdn-technical-writing
- description
- Draft, rewrite, or audit Chinese CSDN-style technical articles using a specific long-form teaching structure: a plain-text overall title, Markdown headings for section levels, dense natural paragraphs, beginner-first progression, commented code examples, and splitting when an article becomes too long. Use for technical tutorials, AI and backend articles, engineering practice notes, and beginner-friendly series.
- license
- MIT
- metadata.author
- Joy T <101039451+FAIRY123456789@users.noreply.github.com>
- metadata.tags
- technical-writing, chinese, csdn
CSDN Technical Writing
Write for a motivated beginner who wants to understand the mechanism, not just copy the code.
Formatting contract
- The article's overall title is plain text, not a Markdown heading.
- First-level sections use
#. - Second-level sections use
##. - Prefer roughly 4–7 first-level sections for a normal article.
- Use full natural paragraphs. Do not split every sentence into a separate paragraph.
- Code goes in fenced code blocks.
- Default to approximately 1,500–2,000 Chinese characters per article, with a 3,000-character maximum unless the user explicitly requests a longer article. Split broader topics into independently useful articles.
- Preserve enough details, working mechanisms, and short commands for a reader to reproduce the core technique. Cut repetition and generic transitions before cutting actionable substance.
Run scripts/lint_csdn_article.py when the draft is available as Markdown.
Private-project anonymization (default, before drafting)
Assume projects, client engagements, school/lab systems, deployments, and source material are private or publication-restricted unless the user explicitly authorizes identifiable publication. A publicly accessible repository, screenshot, or URL does not by itself authorize exposing additional project details in a blog.
Before writing public-facing CSDN text, replace or omit identifying details including:
- Real project/system names and unique aliases, organizations, schools, clients, team members, people, and internal project context.
- Public/private IP addresses, domains, host aliases, SSH usernames, ports used uniquely by the real deployment, instance IDs, and real environment paths, directory names, database/schema/table names.
- Credentials, tokens, passwords, private keys, private API endpoints, internal URLs, unpublished release versions, exact incidents/timestamps, data volumes, performance figures, unpublished architecture specifics, and proprietary model/dataset assets.
- Screenshots, code excerpts, log messages, and comments containing identifying details, including indirect combinations of details that make a project recognizable.
Use generic runnable examples instead: example-app, app_db, app_user, <ECS_HOST>, /opt/example-app/, illustrative ports, fictional filenames, sanitized code comments, and realistic placeholder values. State when a command or configuration is illustrative. Preserve generally reusable technology names and correct mechanisms (Spring Boot, Vue, Flask, Java, MySQL, Nginx, etc.). Never print real secret values even when a project is explicitly public.
For a private project, write a reusable engineering tutorial with anonymized scenarios and no traceable case identifiers. Mention a real project name, exact results, public URLs, or uniquely identifying repository links only with explicit user authorization for those details. If in doubt, generalize without asking the user for private information. Verify titles, prose, tables, code blocks, file paths, captions, and link destinations before publication.
Do not change the actual user's code, server configuration, or repository merely to anonymize a blog; anonymization applies to the published text and examples.
Show full SKILL.md (174 more words)Show less
Teaching sequence
For each important concept:
- Give a formal, accurate definition.
- Explain it again in natural language.
- Explain how it works step by step.
- Explain when it is useful.
- Explain one or two common mistakes or misunderstandings.
- Give a minimal but meaningful code example.
- Comment key lines or explain them immediately after the code.
- Connect the concept to the next concept before introducing new terminology.
Do not stack several unexplained terms in one paragraph.
Paragraph style
- Prefer medium-to-long natural paragraphs when a concept needs continuous explanation.
- Short paragraphs are allowed when they improve code reading or mark a genuine transition.
- Avoid list-heavy article bodies when prose can explain the logic more naturally.
- Avoid repetitive heading formulas such as “为什么……是什么……应该怎样……”. Headings should name the actual technical issue.
- Keep language professional, clear, and approachable. Avoid empty motivational sentences and generic AI conclusions.
Article series
If one topic needs several articles, preserve a clear learning path. Each subarticle should solve one coherent stage and state what prerequisite it assumes.
© FAIRY123456789, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (scripts) in skills/csdn-technical-writing of FAIRY123456789/human-edge-agent-skills.
- SKILL.md
- README.md
- scripts/lint_csdn_article.py
Open the folder on GitHubat commit 31a0a16
Compare with similar skills
Csdn Technical Writing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Csdn Technical Writing this skillFAIRY123456789/human-edge-agent-skills | 103 | — | ~1.3k | Automated safety check: Warn | MIT | |
| JavaScript Concept Fact Checkerleonardomso/33-js-concepts | 67k | 1 repos | ~5k | Automated safety check: Pass | MIT | |
| Beads Documentation Style Guidegastownhall/beads | 28k | — | ~3.2k | Automated safety check: Pass | MIT | |
| JavaScript Concept Page Workflowleonardomso/33-js-concepts | 67k | — | ~3.9k | Automated safety check: Pass | MIT | |
| Technical Writing Standardcursor/plugins | 11k | 10 repos | ~2.3k | Automated safety check: Pass | None | |
| JS Concept Resource Curatorleonardomso/33-js-concepts | 67k | — | ~4.9k | Automated safety check: Pass | MIT |
Similar skills
Beads Documentation Style Guide
gastownhall/beads
Sets the house style for the beads user docs: the canonical concept model, required terminology, prose and diagram conventions, and checks before docs work is done.
JavaScript Concept Page Workflow
leonardomso/33-js-concepts
Orchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO.
- Official
Technical Writing Standard
cursor/plugins
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
JS Concept Resource Curator
leonardomso/33-js-concepts
Finds, vets, writes up and maintains external articles, videos and courses for JavaScript concept pages, including audits for broken and outdated links.
Writing Docs
nukeop/nuclear
A skill your agent uses when writing or editing documentation in packages/docs.
More from FAIRY123456789/human-edge-agent-skills
All 18 skills in this repoAliyun Fullstack Deploy
FAIRY123456789/human-edge-agent-skills
Deploy full-stack apps to user-authorized Alibaba Cloud ECS or comparable Linux VPS hosts with preflight, canary verification, and rollback.
Skill From Scars
FAIRY123456789/human-edge-agent-skills
Mine repeated pain from transcripts, project retrospectives, debugging logs, failed prompts, deployment notes, or work history and decide whether it deserves to become a reusable Agent Skill.
Voice Dump To Todo
FAIRY123456789/human-edge-agent-skills
Convert a long, messy, repetitive, speech-recognition-heavy task dump into a precise executable to-do list.
Deployment Proof
FAIRY123456789/human-edge-agent-skills
Convert deployment logs, validation reports, Git history, and comparison notes into a redacted GitHub case study, portfolio entry, interview story, and evidence-backed resume bullets.
Vibe To Spec
FAIRY123456789/human-edge-agent-skills
Convert messy voice input, imperfect speech recognition, half-formed product ideas, and iterative corrections into an implementation-ready software specification for Codex, Claude Code, Copilot…
Build In Public Launcher
FAIRY123456789/human-edge-agent-skills
Turn a finished or nearly finished Skill, plugin, repository, micro-tool, research utility, or AI project into a credible public launch that can earn real users and feedback.
Related
Categories
Questions about Csdn Technical Writing
What does Csdn Technical Writing do?
Draft, rewrite, or audit Chinese CSDN-style technical articles using a specific long-form teaching structure: a plain-text overall title, Markdown headings for section levels, dense natural…. Csdn Technical Writing is an agent skill from FAIRY123456789/human-edge-agent-skills. Draft, rewrite, or audit Chinese CSDN-style technical articles using a specific long-form teaching structure: a plain-text overall title, Markdown headings for section levels, dense natural paragraphs, beginner-first progression, commented code examples, and splitting when an article becomes too long.
When should I use Csdn Technical Writing?
Csdn Technical Writing fits situations like: technical tutorials; AI and backend articles; engineering practice notes; beginner-friendly series.
How do I install Csdn Technical Writing in Claude Code?
Run `npx skills add FAIRY123456789/human-edge-agent-skills --skill csdn-technical-writing -a claude-code`. Or copy the skill folder (skills/csdn-technical-writing in FAIRY123456789/human-edge-agent-skills) into .claude/skills/csdn-technical-writing in your project. Claude Code loads it when a task matches its description.
How do I install Csdn Technical Writing in Codex?
Run `npx skills add FAIRY123456789/human-edge-agent-skills --skill csdn-technical-writing -a codex`. Or copy the skill folder (skills/csdn-technical-writing in FAIRY123456789/human-edge-agent-skills) into .agents/skills/csdn-technical-writing in your project. Codex loads it when a task matches its description.
Can I use Csdn Technical Writing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FAIRY123456789/human-edge-agent-skills --skill csdn-technical-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/csdn-technical-writing, .gemini/skills/csdn-technical-writing, .github/skills/csdn-technical-writing and .opencode/skills/csdn-technical-writing in your project.
What does Csdn Technical Writing need to run?
Going by SKILL.md and its folder, Csdn Technical Writing needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Csdn Technical Writing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Csdn Technical Writing safe to install?
Our automated static check of SKILL.md flagged 1 warning(s): tells the agent its actions are pre-authorized / not to stop for confirmation. Read the flagged lines before installing; the check is not a guarantee either way. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Csdn Technical Writing use?
Csdn Technical Writing is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Csdn Technical Writing use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Csdn Technical Writing?
Skills that share tags, products or a category with Csdn Technical Writing: JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars), Beads Documentation Style Guide (gastownhall/beads, 28k stars), JavaScript Concept Page Workflow (leonardomso/33-js-concepts, 67k stars) and Technical Writing Standard (cursor/plugins, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Csdn Technical Writing?
FAIRY123456789 (a GitHub user) maintains it in FAIRY123456789/human-edge-agent-skills, which has 103 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 10, 2026.
Source: FAIRY123456789/human-edge-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.