Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Technical Blog Writing
Technical blog post writing with structure, code examples, and developer audience conventions. Covers post types, code formatting, explanation depth, and dev...
skill openclawclawhub Free
Technical blog post writing with structure, code examples, and developer audience conventions. Covers post types, code formatting, explanation depth, and dev...
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.1.5
Provenance
- Publisher
- okaris
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Technical Blog Writing
Write developer-focused technical blog posts via inference.sh CLI.
Quick Start
curl -fsSL https://cli.inference.sh | sh && infsh login # Research topic depth infsh app run exa/search --input '{ "query": "building REST API Node.js best practices 2024 tutorial" }' # Generate header image infsh app run infsh/html-to-image --input '{ "html": "<div style=\"width:1200px;height:630px;background:linear-gradient(135deg,#0f172a,#1e293b);display:flex;align-items:center;padding:60px;font-family:ui-monospace,monospace;color:white\"><div><p style=\"font-size:18px;color:#38bdf8;margin:0\">// engineering blog</p><h1 style=\"font-size:48px;margin:16px 0;font-weight:800;font-family:system-ui;line-height:1.2\">How We Reduced API Latency by 90% with Edge Caching</h1><p style=\"font-size:20px;opacity:0.6;font-family:system-ui\">A deep dive into our CDN architecture</p></div></div>" }' Install note: The install script only detects your OS/architecture, downloads the matching binary from dist.inference.sh, and verifies its SHA-256 checksum. No elevated permissions or background processes. Manual install & verification available.
1. Tutorial / How-To
Step-by-step instruction. The reader should be able to follow along and build something. Structure: 1. What we're building (with screenshot/demo) 2. Prerequisites 3. Step 1: Setup 4. Step 2: Core implementation 5. Step 3: ... 6. Complete code (GitHub link) 7. Next steps / extensions RuleWhyShow the end result firstReader knows if it's worth continuingList prerequisites explicitlyDon't waste time of wrong audienceEvery code block should be runnableCopy-paste-run is the testExplain the "why" not just the "how"Tutorials that explain reasoning get sharedInclude error handlingReal code has errorsLink to complete code repoReference after tutorial
2. Deep Dive / Explainer
Explains a concept, technology, or architecture decision in depth. Structure: 1. What is [concept] and why should you care? 2. How it works (simplified mental model) 3. How it works (detailed mechanics) 4. Real-world example 5. Trade-offs and when NOT to use it 6. Further reading
3. Postmortem / Incident Report
Describes what went wrong, why, and what was fixed. Structure: 1. Summary (what happened, impact, duration) 2. Timeline of events 3. Root cause analysis 4. Fix implemented 5. What we're doing to prevent recurrence 6. Lessons learned
4. Benchmark / Comparison
Data-driven comparison of tools, approaches, or architectures. Structure: 1. What we compared and why 2. Methodology (so results are reproducible) 3. Results with charts/tables 4. Analysis (what the numbers mean) 5. Recommendation (with caveats) 6. Raw data / reproducibility instructions
5. Architecture / System Design
Explains how a system is built and why decisions were made. Structure: 1. Problem we needed to solve 2. Constraints and requirements 3. Options considered 4. Architecture chosen (with diagram) 5. Trade-offs we accepted 6. Results and lessons
Voice and Tone
DoDon'tBe direct: "Use connection pooling""You might want to consider using..."Admit trade-offs: "This adds complexity"Pretend your solution is perfectUse "we" for team decisions"I single-handedly architected..."Specific numbers: "reduced p99 from 800ms to 90ms""significantly improved performance"Cite sources and benchmarksMake unsourced claimsAcknowledge alternativesPretend yours is the only way
What Developers Hate
โ "In today's fast-paced world of technology..." (filler) โ "As we all know..." (if we all know, why are you writing it?) โ "Simply do X" (nothing is simple if you're reading a tutorial) โ "It's easy to..." (dismissive of reader's experience) โ "Obviously..." (if it's obvious, don't write it) โ Marketing language in technical content โ Burying the lede under 3 paragraphs of context
Code Examples
RuleWhyEvery code block must be runnableBroken examples destroy trustShow complete, working examplesSnippets without context are uselessInclude language identifier in fenced blocksSyntax highlightingShow output/result after codeReader verifies understandingUse realistic variable namescalculateTotalRevenue not fooInclude error handling in examplesReal code handles errorsPin dependency versions"Works with React 18.2" not "React" Good code block format: ```python # What this code does (one line) def calculate_retry_delay(attempt: int, base_delay: float = 1.0) -> float: """Exponential backoff with jitter.""" delay = base_delay * (2 ** attempt) jitter = random.uniform(0, delay * 0.1) return delay + jitter # Usage delay = calculate_retry_delay(attempt=3) # ~8.0-8.8 seconds ### Explanation Depth | Audience Signal | Depth | |----------------|-------| | "Getting started with X" | Explain everything, assume no prior knowledge | | "Advanced X patterns" | Skip basics, go deep on nuances | | "X vs Y" | Assume familiarity with both, focus on differences | | "How we built X" | Technical audience, can skip fundamentals | **State your assumed audience level explicitly** at the start: "This post assumes familiarity with Docker and basic Kubernetes concepts. If you're new to containers, start with [our intro post]." ## Blog Post Structure ### The Ideal Structure ```markdown # Title (contains primary keyword, states outcome) [Hero image or diagram] **TL;DR:** [2-3 sentence summary with key takeaway] ## The Problem / Why This Matters [Set up why the reader should care โ specific, not generic] ## The Solution / How We Did It [Core content โ code, architecture, explanation] ### Step 1: [First thing] [Explanation + code + output] ### Step 2: [Second thing] [Explanation + code + output] ## Results [Numbers, benchmarks, outcomes โ be specific] ## Trade-offs and Limitations [Honest about downsides โ builds trust] ## Conclusion [Key takeaway + what to do next] ## Further Reading [3-5 relevant links]
Word Count by Type
TypeWord CountWhyQuick tip500-800One concept, one exampleTutorial1,500-3,000Step-by-step needs detailDeep dive2,000-4,000Thorough explorationArchitecture post2,000-3,500Diagrams carry some loadBenchmark1,500-2,500Data and charts do heavy lifting
When to Use Diagrams
ScenarioDiagram TypeRequest flowSequence diagramSystem architectureBox-and-arrow diagramDecision logicFlowchartData modelER diagramPerformance comparisonBar/line chartBefore/afterSide-by-side # Generate architecture diagram infsh app run infsh/html-to-image --input '{ "html": "<div style=\"width:1200px;height:600px;background:#0f172a;display:flex;align-items:center;justify-content:center;padding:40px;font-family:system-ui;color:white\"><div style=\"display:flex;gap:40px;align-items:center\"><div style=\"background:#1e293b;border:2px solid #334155;border-radius:8px;padding:24px;text-align:center;width:160px\"><p style=\"font-size:14px;color:#94a3b8;margin:0\">Client</p><p style=\"font-size:18px;font-weight:bold;margin:8px 0 0\">React App</p></div><div style=\"color:#64748b;font-size:32px\">โ</div><div style=\"background:#1e293b;border:2px solid #3b82f6;border-radius:8px;padding:24px;text-align:center;width:160px\"><p style=\"font-size:14px;color:#94a3b8;margin:0\">Edge</p><p style=\"font-size:18px;font-weight:bold;margin:8px 0 0\">CDN Cache</p></div><div style=\"color:#64748b;font-size:32px\">โ</div><div style=\"background:#1e293b;border:2px solid #334155;border-radius:8px;padding:24px;text-align:center;width:160px\"><p style=\"font-size:14px;color:#94a3b8;margin:0\">API</p><p style=\"font-size:18px;font-weight:bold;margin:8px 0 0\">Node.js</p></div><div style=\"color:#64748b;font-size:32px\">โ</div><div style=\"background:#1e293b;border:2px solid #334155;border-radius:8px;padding:24px;text-align:center;width:160px\"><p style=\"font-size:14px;color:#94a3b8;margin:0\">Database</p><p style=\"font-size:18px;font-weight:bold;margin:8px 0 0\">PostgreSQL</p></div></div></div>" }' # Generate benchmark chart infsh app run infsh/python-executor --input '{ "code": "import matplotlib.pyplot as plt\nimport matplotlib\nmatplotlib.use(\"Agg\")\n\nfig, ax = plt.subplots(figsize=(12, 6))\nfig.patch.set_facecolor(\"#0f172a\")\nax.set_facecolor(\"#0f172a\")\n\ntools = [\"Express\", \"Fastify\", \"Hono\", \"Elysia\"]\nrps = [15000, 45000, 62000, 78000]\ncolors = [\"#64748b\", \"#64748b\", \"#3b82f6\", \"#64748b\"]\n\nax.barh(tools, rps, color=colors, height=0.5)\nfor i, v in enumerate(rps):\n ax.text(v + 1000, i, f\"{v:,} req/s\", va=\"center\", color=\"white\", fontsize=14)\n\nax.set_xlabel(\"Requests per second\", color=\"white\", fontsize=14)\nax.set_title(\"HTTP Framework Benchmark (Hello World)\", color=\"white\", fontsize=18, fontweight=\"bold\")\nax.tick_params(colors=\"white\", labelsize=12)\nax.spines[\"top\"].set_visible(False)\nax.spines[\"right\"].set_visible(False)\nax.spines[\"bottom\"].set_color(\"#334155\")\nax.spines[\"left\"].set_color(\"#334155\")\nplt.tight_layout()\nplt.savefig(\"benchmark.png\", dpi=150, facecolor=\"#0f172a\")\nprint(\"Saved\")" }'
Where Developers Read
PlatformFormatHow to PostYour blogFull articlePrimary โ own your contentDev.toCross-post (canonical URL back to yours)Markdown importHashnodeCross-post (canonical URL)Markdown importHacker NewsLink submissionShow HN for projects, tell HN for storiesReddit (r/programming, r/webdev, etc.)Link or discussionFollow subreddit rulesTwitter/XThread summary + linkSee twitter-thread-creation skillLinkedInAdapted version + linkSee linkedin-content skill # Cross-post thread to X infsh app run x/post-create --input '{ "text": "New blog post: How We Reduced API Latency by 90%\n\nThe short version:\nโ Moved computation to edge\nโ Aggressive cache-control headers\nโ Eliminated N+1 queries\n\np99 went from 800ms to 90ms.\n\nFull deep dive with code: [link]" }'
Common Mistakes
MistakeProblemFixNo TL;DRBusy devs leave before getting the point2-3 sentence summary at the topBroken code examplesDestroys all credibilityTest every code block before publishingNo version pinningCode breaks in 6 months"Works with Node 20, React 18.2""Simply do X"Dismissive, condescendingRemove "simply", "just", "easily"No diagrams for architectureWalls of text describing systemsOne diagram > 500 words of descriptionMarketing toneDevelopers instantly disengageDirect, technical, honestNo trade-offs sectionReads as biased marketingAlways discuss downsidesGiant introduction before contentReaders bounceGet to the point in 2-3 paragraphsUnpinned dependenciesTutorial breaks for future readersPin versions, note date writtenNo "Further Reading"Dead end, no context3-5 links to deepen understanding
Related Skills
npx skills add inference-sh/skills@seo-content-brief npx skills add inference-sh/skills@content-repurposing npx skills add inference-sh/skills@og-image-design Browse all apps: infsh app list
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md