Skills
Technical Blog Writing
by inference.sh
Write technical blog posts for developers: post types, code examples, explanation depth and structure.
Our verdict
We have not reviewed Technical Blog Writing yet
No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.
From the listing
About Technical Blog Writing
A writing guide from inference.sh for developer content. It covers post types such as tutorials and deep dives, how to format and introduce code examples, how much to explain for the audience, and structure that keeps developers reading. Drafting runs through the inference.sh belt CLI.
Best for
Developer relations and engineering teams writing technical posts
Use cases
- Write a tutorial post that readers can follow and build from
- Turn an engineering change into a blog post
- Plan the structure of a deep dive
Notes
Why it matters
Technical posts lose readers when code is unexplained or the depth is wrong for the audience. This guide sets those choices before writing starts.
Source
- Skill file: guides/writing/technical-blog-writing/SKILL.md in inference-sh/skills.
- Repository: 778 GitHub stars, no licence file in the repository. Checked 24 Oct 2026 through the GitHub API.
- Last change to the skill: 3 Aug 2026.
- This page was written from the skill's own SKILL.md. It is not an Enterprise DNA source review and the skill has not been installed or tested by us.
Pros
- Clear post types with rules and reasons
- Developer-specific conventions
- Part of a larger guide library
Cons
- Drafting needs the inference.sh CLI
- No licence file in the repository
Key facts
What we have checked
- Days since the last commit
- 30
- GitHub forks
- 109
- GitHub stars
- 808
- Days to a first reply on issues
- 36.4
- Open issues
- 4
- Releases in the last 90 days
- 0
Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.
Stars and usage
How Technical Blog Writing is growing
795 to 808
Health and security
Is Technical Blog Writing looked after, and what do its setup files show
Health score
56 out of 100
| Part | Points | What we saw |
|---|---|---|
| Recent activity | 30 of 30 | Last push 30 days ago |
| Releases | 0 of 15 | 0 releases in 90 days |
| Issue replies | 0 of 20 | First reply in 36.4 days (median) |
| Maintainer | 15 of 15 | Owned by an organisation |
| Official source | Not counted | MCP servers only |
Security check static checks
100 out of 100
- Note 1 of 1 packages are not pinned to one version, so only the malicious packages list was checked for them, not version advisories.
Sources
Where this comes from
- GitHubRegistry
A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.
Changelog
What changed
No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Article Writing
affaan-m
Write long-form articles, guides and newsletters in a voice taken from your examples, with proof instead of adjectives.
copy-editing
coreyhaines31
Marketing skills for Claude Code and AI agents. CRO, copywriting, SEO, analytics, and growth engineering.
technical-writing
michael-denyer
Antigravity, Claude Code, Codex, Copilot, Gemini, Muse, OpenCode, Pi, and Prime Agent versions of Poteto's pstack. Rigorous agent workflows with Cursor primitives translated for ot
writing-skills
obra
An agentic skills framework & software development methodology that works.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.