Khazix WeChat Article Writer
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
When the user wants to create technical content for developers including blog posts, tutorials, and documentation.
$ npx skills add sickn33/agentic-awesome-skills --skill devrel-content -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills devrel-content --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/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/devrel-content .claude/skills/devrel-content && 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 "devrel-content" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/devrel-content into .claude/skills/devrel-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devrel-content", 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/sickn33/agentic-awesome-skills/tree/main/skills/devrel-contentType 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 sickn33/agentic-awesome-skills --skill devrel-content -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills devrel-content --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/devrel-content .agents/skills/devrel-content && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "devrel-content" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/devrel-content into .agents/skills/devrel-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devrel-content", 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 sickn33/agentic-awesome-skills --skill devrel-content -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills devrel-content --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/devrel-content .cursor/skills/devrel-content && 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 "devrel-content" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/devrel-content into .cursor/skills/devrel-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devrel-content", 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/sickn33/agentic-awesome-skills.git --path skills/devrel-content--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 sickn33/agentic-awesome-skills --skill devrel-content -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills devrel-content --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/devrel-content .gemini/skills/devrel-content && 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 "devrel-content" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/devrel-content into .gemini/skills/devrel-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devrel-content", 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 sickn33/agentic-awesome-skills devrel-contentInstalls 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 sickn33/agentic-awesome-skills --skill devrel-content -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/devrel-content .github/skills/devrel-content && 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 "devrel-content" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/devrel-content into .github/skills/devrel-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devrel-content", 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 sickn33/agentic-awesome-skills --skill devrel-content -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills devrel-content --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/devrel-content .opencode/skills/devrel-content && 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 "devrel-content" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/devrel-content into .opencode/skills/devrel-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devrel-content", 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.
devrel-contentWhen the user wants to create technical content for developers including blog posts, tutorials, and documentation.
Devrel Content is an agent skill from sickn33/agentic-awesome-skills. When the user wants to create technical content for developers including blog posts, tutorials, and documentation.
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).
It sits in Writing & Content, covering Blog and article writing. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 1e53ce2. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
npmpipgocargoFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
octolens.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Devrel Content loads about 3k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 1,015 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.
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.
The full file from sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 1,015 words, ~3,013 tokens.
.claude/skills/devrel-content/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Use this skill when you need when the user wants to create technical content for developers including blog posts, tutorials, and documentation. Trigger phrases include "write a blog post," "technical article," "developer content," "tutorial," "devrel content," "dev blog," "technical writing," or "content for...
This skill helps you create technical content that developers actually read: blog posts, tutorials, documentation, and thought leadership pieces that build trust and drive adoption.
Load your audience context first. Read .agents/developer-audience-context.md to understand:
If the context file doesn't exist, run the developer-audience-context skill first.
Before writing anything, validate the topic is worth writing about.
| Research Type | What to Do |
|---|---|
| Search intent | Google your topic. What already ranks? What's missing? |
| Community signals | Search Reddit, HN, Stack Overflow. Are developers asking about this? |
| Competitor gaps | What have competitors written? What haven't they covered? |
| Internal data | Support tickets, Discord questions, GitHub issues about this topic |
| Keyword research | Use Ahrefs/SEMrush for search volume on technical terms |
Red flags — Don't write if:
Choose the right format for your goal:
| Content Type | Best For | Structure |
|---|---|---|
| Tutorial | Teaching a specific skill | Step-by-step, code-heavy |
| Guide | Covering a topic comprehensively | Sections, reference material |
| Comparison | Helping with decisions | Table-based, pros/cons |
| Announcement | Launching features/products | News lead, what/why/how |
| Thought leadership | Building authority | Opinion, predictions, takes |
| Case study | Social proof | Problem → Solution → Results |
| Troubleshooting | Solving specific errors | Error → Cause → Fix |
Use this outline template:
# [Title that promises specific value]
## Hook (2-3 sentences)
- State the problem or opportunity
- Establish credibility ("We migrated 10,000 repos...")
- Promise what the reader will learn
## Context (optional)
- Brief background if needed
- Link to prerequisites
## The Meat
### Section 1: [First major concept]
- Explanation
- Code example
- Common pitfall
### Section 2: [Second major concept]
- Explanation
- Code example
- Real-world application
### Section 3: [Third major concept]
- Explanation
- Code example
- Advanced tip
## Putting It Together
- Complete example
- Working code
## What's Next
- Links to deeper content
- Call to action (try the product, join Discord, etc.)Code is the content. Get it right.
Every code example must:
| Requirement | Why It Matters |
|---|---|
| Run without modification | Developers will copy-paste. If it fails, you lose trust. |
| Include imports | Don't assume they know which libraries to import. |
| Show output | What should they see when it works? |
| Handle errors | Real code has error handling. Show it. |
| Use real values | No foo, bar, example.com unless necessary. |
First, install the dependencies:
\`\`\`bash
npm install your-library axios
\`\`\`
Now create a file called `fetch-data.js`:
\`\`\`javascript
// fetch-data.js
import { Client } from 'your-library';
import axios from 'axios';
const client = new Client({
apiKey: process.env.YOUR_API_KEY // Use environment variables
});
async function fetchUserData(userId) {
try {
const user = await client.users.get(userId);
console.log(`Fetched user: ${user.name}`);
return user;
} catch (error) {
console.error(`Failed to fetch user: ${error.message}`);
throw error;
}
}
// Example usage
fetchUserData('user_123')
.then(user => console.log(user))
.catch(err => process.exit(1));
\`\`\`
Run it:
\`\`\`bash
YOUR_API_KEY=sk_test_xxx node fetch-data.js
\`\`\`
Expected output:
\`\`\`
Fetched user: Jane Developer
{ id: 'user_123', name: 'Jane Developer', email: 'jane@example.dev' }
\`\`\`| Language | Code Block | Package Install | Env Vars |
|---|---|---|---|
| JavaScript/Node | javascript or js | npm install | process.env.VAR |
| TypeScript | typescript or ts | npm install | process.env.VAR |
| Python | python or py | pip install | os.environ['VAR'] |
| Go | go | go get | os.Getenv("VAR") |
| Rust | rust | cargo add | std::env::var("VAR") |
| Shell | bash or shell | N/A | $VAR |
Run through before publishing:
| Check | How to Verify |
|---|---|
| Code runs | Copy-paste every snippet and run it |
| Versions match | Are you using the current library version? |
| Links work | Click every link |
| Commands work | Run every CLI command |
| Screenshots current | Do UI screenshots match the current product? |
| No deprecated APIs | Check if any APIs used are deprecated |
| Security review | No hardcoded secrets, SQL injection, etc. |
| Peer review | Have an engineer read it for accuracy |
Developers use Google differently than consumers.
| Pattern | Example Searches |
|---|---|
| Error messages | "TypeError: Cannot read property 'map' of undefined" |
| How to | "how to deploy next.js to vercel" |
| Comparison | "prisma vs typeorm 2024" |
| Best practices | "typescript project structure best practices" |
| Alternatives | "alternatives to firebase" |
| With | "react with typescript tutorial" |
| Element | Best Practice |
|---|---|
| Title | Include primary keyword, framework names, year if relevant |
| Meta description | 150 chars, include keyword, promise specific outcome |
| H1 | Match or closely match title |
| H2s | Include secondary keywords, make scannable |
| Code blocks | Use proper syntax highlighting (helps featured snippets) |
| Internal links | Link to related docs, tutorials, API reference |
| External links | Link to official docs of tools mentioned |
| URL slug | Lowercase, hyphens, include keyword |
| Bad | Good |
|---|---|
| "Using Our API" | "How to Authenticate with the YourProduct API (Node.js)" |
| "Database Guide" | "PostgreSQL Connection Pooling: Complete Guide with pgBouncer" |
| "Getting Started" | "Getting Started with YourProduct: Your First API Call in 5 Minutes" |
What separates great devrel content from mediocre:
# [Specific, keyword-rich title]
[2-3 sentence hook: problem + promise]
## The Problem
[1 paragraph explaining the pain point]
## The Solution
[Brief explanation of your approach]
### Step 1: [Action]
[Explanation]
\`\`\`language
// Code
\`\`\`
### Step 2: [Action]
[Explanation]
\`\`\`language
// Code
\`\`\`
### Step 3: [Action]
[Explanation]
\`\`\`language
// Code
\`\`\`
## Complete Example
\`\`\`language
// Full working code
\`\`\`
## Troubleshooting
### [Common Error 1]
[Solution]
### [Common Error 2]
[Solution]
## What's Next
- [Link to deeper dive]
- [Link to related tutorial]
- [CTA: Try it yourself]# [Tool A] vs [Tool B]: [Specific Use Case] ([Year])
[1 paragraph: Who this comparison is for and what you'll learn]
## Quick Comparison
| Feature | Tool A | Tool B |
|---------|--------|--------|
| [Feature 1] | | |
| [Feature 2] | | |
| [Feature 3] | | |
## When to Choose [Tool A]
- [Scenario 1]
- [Scenario 2]
- [Scenario 3]
## When to Choose [Tool B]
- [Scenario 1]
- [Scenario 2]
- [Scenario 3]
## Deep Dive: [Specific Aspect]
### Tool A Approach
[Explanation + code]
### Tool B Approach
[Explanation + code]
## Our Recommendation
[Specific guidance based on use case]| Metric | What It Tells You |
|---|---|
| Page views | Reach (but vanity without context) |
| Time on page | Engagement (are they reading?) |
| Scroll depth | Did they read to the end? |
| Bounce rate | Did they find what they needed? |
| Search rankings | SEO performance |
| Backlinks | Authority and reference value |
| Social shares | Resonance (especially HN, Twitter, Reddit) |
| Conversion events | Sign-ups, installs, docs clicks |
Track the journey:
| Tool | Use Case |
|---|---|
| Octolens | Monitor where your content gets shared (HN, Reddit, Twitter). Track competitor content performance. Find content ideas from developer conversations. |
| Grammarly / Hemingway | Readability and grammar checking |
| Carbon / Ray.so | Beautiful code screenshots |
| Excalidraw | Technical diagrams |
| Loom | Quick video walkthroughs |
| Ahrefs / SEMrush | Keyword research and SEO tracking |
| Google Search Console | Track search performance |
developer-audience-context — Foundation for knowing your readerstechnical-tutorials — Deep dive into step-by-step contentdeveloper-newsletter — Distributing content via emaildeveloper-seo — Technical SEO optimizationhacker-news-strategy — Sharing content on HN effectively© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/devrel-content of sickn33/agentic-awesome-skills.
Open the folder on GitHubat commit 1e53ce2
We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
Devrel Content 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 |
|---|---|---|---|---|---|---|
| Devrel Content this skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~3k | Automated safety check: Pass | MIT | |
| Khazix WeChat Article WriterKKKKhazix/khazix-skills | 21k | 2 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Figurevectorize-io/hindsight | 46k | — | ~1.9k | Automated safety check: Pass | MIT | |
| SepiaNanako0129/sepia | 3k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Blog Post Draftingluongnv89/claude-howto | 42k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Notion To Blogwasp-lang/wasp | 19k | — | ~922 | Automated safety check: Pass | MIT |
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
vectorize-io/hindsight
Draw an animated figure (boxes, arrows, moving data) as one self-contained SVG for a GitHub README, PR, issue or blog post.
Nanako0129/sepia
Make AI-generated writing read as human-written, in fiction and in professional prose.
luongnv89/claude-howto
Guides drafting a blog post from an idea and optional source material: research, brainstorming, outlining and version-tracked drafts, with user approval at each step.
wasp-lang/wasp
Transfer a blog post from Notion to the Wasp blog. An agent skill from wasp-lang/wasp.
aiworkskills/wechat-article-skills
Rewrites, continues, or polishes an existing WeChat article draft using a configurable language model, sending the full draft text to that endpoint.
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
sickn33/agentic-awesome-skills
Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Categories
When the user wants to create technical content for developers including blog posts, tutorials, and documentation. Devrel Content is an agent skill from sickn33/agentic-awesome-skills. When the user wants to create technical content for developers including blog posts, tutorials, and documentation.
Devrel Content fits situations like: wants to create technical content for developers including blog posts; tasks that involve Blog and article writing.
Run `npx skills add sickn33/agentic-awesome-skills --skill devrel-content -a claude-code`. Or copy the skill folder (skills/devrel-content in sickn33/agentic-awesome-skills) into .claude/skills/devrel-content in your project. Claude Code loads it when a task matches its description.
Run `npx skills add sickn33/agentic-awesome-skills --skill devrel-content -a codex`. Or copy the skill folder (skills/devrel-content in sickn33/agentic-awesome-skills) into .agents/skills/devrel-content in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill devrel-content -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/devrel-content, .gemini/skills/devrel-content, .github/skills/devrel-content and .opencode/skills/devrel-content in your project.
Going by SKILL.md and its folder, Devrel Content needs the command-line tools its instructions call (npm, pip, go and cargo). Our summary lists: Python 3; Node.js; A credential in YOUR_API_KEY.
SKILL.md names 1 domain. As links in the text: octolens.com. This is read from the text; nothing was executed.
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.
Devrel Content is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3k 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.
Skills that share tags, products or a category with Devrel Content: Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars), Figure (vectorize-io/hindsight, 46k stars), Sepia (Nanako0129/sepia, 3k stars) and Blog Post Drafting (luongnv89/claude-howto, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.