How do I install the Blog Post skill?

Run npx skillmds@latest add tomevault-io/blog-post in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Blog Post safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Blog Post?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Blog Post free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Blog Post?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Blog Post by tomevault-io — Agent Skill

Name: Blog Post
Author: tomevault-io

Blog Post

Draft, edit, and publish blog posts for e9n.dev. Use when creating new posts, editing drafts, or refining existing content. Handles Eleventy frontmatter, Tailwind formatting, and Espen's authentic voice. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Blog Post — e9n.dev

Write and publish blog posts for Espen's blog at /Users/espen/Dev/e9n.dev/.

Voice & Style

Espen's writing style:

Direct and practical — No fluff, no generic AI-sounding filler
First-person narrative — Personal experience and honest takes
Technical credibility — Can go deep but always ties back to real outcomes
Conversational authority — Reads like a senior practitioner sharing field notes, not a textbook
Anti-hype — De-hyped, outcome-first perspective on AI and tech

Avoid:

"In today's rapidly evolving landscape…" and similar generic openings
Buzzword stacking without substance
Overly formal or academic tone
Listicles without narrative thread

Process

Read existing posts to match voice and format:
```
ls /Users/espen/Dev/e9n.dev/src/posts/
```
Read 2-3 recent posts to calibrate tone.
Create the post file using the project's naming convention:
```
/Users/espen/Dev/e9n.dev/src/posts/YYYY-MM-DD-slug.md
```

Frontmatter template:

---
title: "Post Title"
description: "One-line description for SEO and social sharing"
date: YYYY-MM-DD
tags:
  - ai
  - sales
  - self-growth
---

Structure:
- Hook in the first paragraph (personal anecdote, bold claim, or question)
- 2-4 main sections with practical takeaways
- Concrete examples, code snippets, or frameworks where relevant
- Close with a next action or reflection, not a generic summary
Review checklist:
- Does it sound like Espen, not an AI?
- Is there a concrete takeaway in every section?
- Would a senior technical/sales reader find this worth their time?
- Is the frontmatter complete (title, description, date, tags)?

Preview

cd /Users/espen/Dev/e9n.dev && npm run dev

Common Tags

ai, sales, self-growth, agentic-ai, productivity, leadership, stoicism, infrastructure, devops, typescript

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: blog-postdescription: Draft, edit, and publish blog posts for e9n.dev. Use when creating new posts, editing drafts, or refining existing content. Handles Eleventy frontmatter, Tailwind formatting, and Espen's authentic voice. Use when this capability is needed.---# Blog Post — e9n.devWrite and publish blog posts for Espen's blog at `/Users/espen/Dev/e9n.dev/`.## Voice & StyleEspen's writing style:- **Direct and practical** — No fluff, no generic AI-sounding filler- **First-person narrative** — Personal experience and honest takes- **Technical credibility** — Can go deep but always ties back to real outcomes- **Conversational authority** — Reads like a senior practitioner sharing field notes, not a textbook- **Anti-hype** — De-hyped, outcome-first perspective on AI and techAvoid:- "In today's rapidly evolving landscape…" and similar generic openings- Buzzword stacking without substance- Overly formal or academic tone- Listicles without narrative thread## Process1. **Read existing posts** to match voice and format: ```bash ls /Users/espen/Dev/e9n.dev/src/posts/ ``` Read 2-3 recent posts to calibrate tone.2. **Create the post file** using the project's naming convention: ``` /Users/espen/Dev/e9n.dev/src/posts/YYYY-MM-DD-slug.md ```3. **Frontmatter template:** ```yaml --- title: "Post Title" description: "One-line description for SEO and social sharing" date: YYYY-MM-DD tags: - ai - sales - self-growth --- ```4. **Structure:** - Hook in the first paragraph (personal anecdote, bold claim, or question) - 2-4 main sections with practical takeaways - Concrete examples, code snippets, or frameworks where relevant - Close with a next action or reflection, not a generic summary5. **Review checklist:** - [ ] Does it sound like Espen, not an AI? - [ ] Is there a concrete takeaway in every section? - [ ] Would a senior technical/sales reader find this worth their time? - [ ] Is the frontmatter complete (title, description, date, tags)?## Preview```bashcd /Users/espen/Dev/e9n.dev && npm run dev```## Common Tags`ai`, `sales`, `self-growth`, `agentic-ai`, `productivity`, `leadership`, `stoicism`, `infrastructure`, `devops`, `typescript`---> Converted and distributed by [TomeVault](https://tomevault.io/claim/espennilsen) — claim your Tome and manage your conversions.

Frequently asked questions