Docs Lead
lablup/backend.ai-webui
A skill your agent uses whenever the user mentions docs, the manual, documentation, terminology, translations, or screenshots — including indirect mentions like "이 PR 문서 영향 봐줘", "문서 점검", "용어 통일"…
Technical blog post writing with structure, code examples, and developer audience conventions.
Install Technical Blog Writing
$ npx skills add NeverSight/learn-skills.dev --skill technical-blog-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NeverSight/learn-skills.dev technical-blog-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/NeverSight/learn-skills.dev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/data/skills-md/101-skills/skills/technical-blog-writing .claude/skills/technical-blog-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 "technical-blog-writing" agent skill from https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/101-skills/skills/technical-blog-writing into .claude/skills/technical-blog-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-blog-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/NeverSight/learn-skills.dev/tree/main/data/skills-md/101-skills/skills/technical-blog-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 NeverSight/learn-skills.dev --skill technical-blog-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NeverSight/learn-skills.dev technical-blog-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NeverSight/learn-skills.dev.git skills-src && mkdir -p .agents/skills && cp -r skills-src/data/skills-md/101-skills/skills/technical-blog-writing .agents/skills/technical-blog-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 "technical-blog-writing" agent skill from https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/101-skills/skills/technical-blog-writing into .agents/skills/technical-blog-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-blog-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 NeverSight/learn-skills.dev --skill technical-blog-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NeverSight/learn-skills.dev technical-blog-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NeverSight/learn-skills.dev.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/data/skills-md/101-skills/skills/technical-blog-writing .cursor/skills/technical-blog-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 "technical-blog-writing" agent skill from https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/101-skills/skills/technical-blog-writing into .cursor/skills/technical-blog-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-blog-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/NeverSight/learn-skills.dev.git --path data/skills-md/101-skills/skills/technical-blog-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 NeverSight/learn-skills.dev --skill technical-blog-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NeverSight/learn-skills.dev technical-blog-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NeverSight/learn-skills.dev.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/data/skills-md/101-skills/skills/technical-blog-writing .gemini/skills/technical-blog-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 "technical-blog-writing" agent skill from https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/101-skills/skills/technical-blog-writing into .gemini/skills/technical-blog-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-blog-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 NeverSight/learn-skills.dev technical-blog-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 NeverSight/learn-skills.dev --skill technical-blog-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NeverSight/learn-skills.dev.git skills-src && mkdir -p .github/skills && cp -r skills-src/data/skills-md/101-skills/skills/technical-blog-writing .github/skills/technical-blog-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 "technical-blog-writing" agent skill from https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/101-skills/skills/technical-blog-writing into .github/skills/technical-blog-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-blog-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 NeverSight/learn-skills.dev --skill technical-blog-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 NeverSight/learn-skills.dev technical-blog-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NeverSight/learn-skills.dev.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/data/skills-md/101-skills/skills/technical-blog-writing .opencode/skills/technical-blog-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 "technical-blog-writing" agent skill from https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/101-skills/skills/technical-blog-writing into .opencode/skills/technical-blog-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-blog-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
technical-blog-writing- GitHub stars
- 216
- Used in
- 1 other repo
- Token cost
- ~3.1k tokens
- SKILL.md length
- 579 words
- Files
- 13
- Skills in repo
- 42
- Repo updated
- First seen
- Licence
- None found
At a glance
Technical blog post writing with structure, code examples, and developer audience conventions.
- Works in 5 steps: Tutorial / How-To → Deep Dive / Explainer → Postmortem / Incident Report → …
- : engineering blogs
- SKILL.md covers Quick Start, Post Types, Writing Rules for Developers and Diagrams and Visuals, plus 3 more sections
- Calls npx
What it does
Technical Blog Writing is an agent skill from NeverSight/learn-skills.dev. Technical blog post writing with structure, code examples, and developer audience conventions. Covers post types, code formatting, explanation depth, and developer-specific engagement patterns. Use for: engineering blogs, dev tutorials, technical writing, developer content, documentation posts. Triggers: technical blog, dev blog, engineering blog, technical writing, developer tutorial, tech post, code tutorial, programming blog, developer content, technical article, engineering post, coding tutorial, technical…
Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files (for example `stats.json`).
It sits in Writing & Content, covering Blog and article writing, Technical writing and Linting and formatting. The repository describes itself as: Curated high-quality AI Agent Skills. Search, install, copy and share. Works with Claude Code, Cursor, OpenClaw, and other AI coding tools.
When your agent uses it
- : engineering blogs
- Technical writing
- Developer content
- Documentation posts
Example prompts
- “/technical-blog-writing”
Requirements
- Python 3
- Node.js
- Docker
- Pre-approved tools (allowed-tools): Bash(belt *)
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Tutorial / How-To
- Deep Dive / Explainer
- Postmortem / Incident Report
- Benchmark / Comparison
- Architecture / System Design
What it can do on your machine
Read from SKILL.md and the folder at commit 50f7fc9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(belt *)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
inference.shraw.githubusercontent.com
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
Technical Blog Writing loads about 3.1k tokens when it runs. Until then it costs about 137 tokens; SKILL.md has 579 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 passed
The automated check found no risky patterns in SKILL.md.
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); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 579 words (~3,069 tokens).
“Write developer-focused technical blog posts via inference.sh CLI.”
- name
- technical-blog-writing
- allowed-tools
- Bash(belt *)
Files
SKILL.md and 12 other files in data/skills-md/101-skills/skills/technical-blog-writing of NeverSight/learn-skills.dev.
- SKILL.md
- description_ar.txt
- description_cn.txt
- description_de.txt
- description_en.txt
- description_es.txt
- description_fr.txt
- description_it.txt
- description_ja.txt
- description_ko.txt
- description_ru.txt
- description_tw.txt
- stats.json
Open the folder on GitHubat commit 50f7fc9
Used in 1 other repository
We found 8 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in NeverSight/learn-skills.dev, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Technical Blog 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 |
|---|---|---|---|---|---|---|
| Technical Blog Writing this skillNeverSight/learn-skills.dev | 216 | 1 repos | ~3.1k | Automated safety check: Pass | None | |
| Docs Leadlablup/backend.ai-webui | 133 | — | ~2.9k | Automated safety check: Pass | LGPL-3.0 | |
| Rnd Technical Writerchendongqi/OPB-Skills | 125 | — | ~2.5k | Automated safety check: Pass | None | |
| Dynamo Content DesignerDynamoDS/Dynamo | 2k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Voicejvm-skills/jvm-skills | 140 | — | ~592 | Automated safety check: Pass | Apache-2.0 | |
| Domodomo Release Documentationdarknecrocities/DomoDomo---All-in-one-Tool | 239 | — | ~17k | Automated safety check: Pass | None |
Similar skills
Rnd Technical Writer
chendongqi/OPB-Skills
Technical article writing assistant. An agent skill from chendongqi/OPB-Skills.
Dynamo Content Designer
DynamoDS/Dynamo
Technical writing specialist for Dynamo product documentation, blog posts, tutorials, and educational content.
Voice
jvm-skills/jvm-skills
Make prose sound like Thomas, not like a generic technical writer.
Domodomo Release Documentation
darknecrocities/DomoDomo---All-in-one-Tool
Maintain DomoDomo product documentation, technical tool records, About metrics, blog posts, SEO metadata, sitemap generation, release communication, and contributor guidance.
Reading Level
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing content pages for user experience and SEO.
More from NeverSight/learn-skills.dev
All 42 skills in this repoAI Marketing Videos
NeverSight/learn-skills.dev
Create AI marketing videos for ads, promos, product launches, and brand content.
Google Calendar
NeverSight/learn-skills.dev
Interact with Google Calendar via the Google Calendar API – list upcoming events, create new events, update or delete them.
Agent Orchestrator
NeverSight/learn-skills.dev
Meta-agent skill for orchestrating complex tasks through autonomous sub-agents.
AI Automation Workflows
NeverSight/learn-skills.dev
Build automated AI workflows combining multiple models and services.
AI Content Pipeline
NeverSight/learn-skills.dev
Build multi-step AI content creation pipelines combining image, video, audio, and text.
AI Podcast Creation
NeverSight/learn-skills.dev
Create AI-powered podcasts with text-to-speech, music, and audio editing.
Related
Categories
Questions about Technical Blog Writing
What does Technical Blog Writing do?
Technical blog post writing with structure, code examples, and developer audience conventions. dev. Technical blog post writing with structure, code examples, and developer audience conventions.
When should I use Technical Blog Writing?
Technical Blog Writing fits situations like: : engineering blogs; technical writing; developer content; documentation posts.
How do I install Technical Blog Writing in Claude Code?
Run `npx skills add NeverSight/learn-skills.dev --skill technical-blog-writing -a claude-code`. Or copy the skill folder (data/skills-md/101-skills/skills/technical-blog-writing in NeverSight/learn-skills.dev) into .claude/skills/technical-blog-writing in your project. Claude Code loads it when a task matches its description.
How do I install Technical Blog Writing in Codex?
Run `npx skills add NeverSight/learn-skills.dev --skill technical-blog-writing -a codex`. Or copy the skill folder (data/skills-md/101-skills/skills/technical-blog-writing in NeverSight/learn-skills.dev) into .agents/skills/technical-blog-writing in your project. Codex loads it when a task matches its description.
Can I use Technical Blog 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 NeverSight/learn-skills.dev --skill technical-blog-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/technical-blog-writing, .gemini/skills/technical-blog-writing, .github/skills/technical-blog-writing and .opencode/skills/technical-blog-writing in your project.
What does Technical Blog Writing need to run?
Going by SKILL.md and its folder, Technical Blog Writing needs the command-line tools its instructions call (npx). Our summary lists: Python 3; Node.js; Docker. Its frontmatter pre-approves these tools: Bash(belt *).
Does Technical Blog Writing access the network?
SKILL.md names 2 domains. As links in the text: inference.sh and raw.githubusercontent.com. This is read from the text; nothing was executed.
Is Technical Blog Writing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Technical Blog Writing use?
No licence was found for Technical Blog Writing or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Technical Blog Writing use?
About 3.1k tokens (SKILL.md is roughly 12k 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 Technical Blog Writing?
Skills that share tags, products or a category with Technical Blog Writing: Docs Lead (lablup/backend.ai-webui, 133 stars), Rnd Technical Writer (chendongqi/OPB-Skills, 125 stars), Dynamo Content Designer (DynamoDS/Dynamo, 2k stars) and Voice (jvm-skills/jvm-skills, 140 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Technical Blog Writing?
NeverSight (a GitHub organization) maintains it in NeverSight/learn-skills.dev, which has 216 GitHub stars. The repository holds 42 skills in this directory. The repository was last updated on October 9, 2026.
Source: NeverSight/learn-skills.dev on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.