Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

  1. Read existing posts to match voice and format:

    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:

    ---
    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 summary
  5. 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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Audit, generate, update, and lint AGENTS.md files across all projects. Use when asked to check project context files, scaffold AGENTS.md for new projects, update stale ones, or run a cross-project audit.

The English summary is being prepared. Showing the original description.

espennilsen/pi122Updated Oct 12, 2026

Generate a full operational status report for the Aivena bot. Checks all subsystems: extensions, webserver, Telegram, chat bridge, heartbeat, cron, database, memory, CRM, calendar, task management, jobs/telemetry, and storage. **Triggers — use this skill when:** - User asks for "status", "bot status", "system status", "operational status" - User asks "is everything running?", "how's Aivena doing?" - User says "health check", "diagnostics", "systems check" - User asks "what's the state of the bot?"

The English summary is being prepared. Showing the original description.

espennilsen/pi122Updated Oct 12, 2026

Parse git history and produce or update a CHANGELOG.md following the Keep a Changelog convention. Supports Conventional Commits, basic prefix conventions, and unstructured commit messages. Intelligently categorizes changes, detects breaking changes, links to PRs/issues, and handles both initial generation and incremental updates. **Triggers — use this skill when:** - User asks to "generate", "create", "update", or "write" a changelog - User mentions "CHANGELOG", "changelog", "release notes" - User says "document changes", "what changed since last release" - User wants to "prepare a release" and needs a changelog entry - User asks to "clean up" or "reformat" an existing changelog **Covers:** Any git-based project. Handles Conventional Commits (feat/fix/chore), Angular convention, basic prefixes (Add/Fix/Remove), and freeform commit messages. Outputs Keep a Changelog format with optional Common Changelog enhancements.

The English summary is being prepared. Showing the original description.

espennilsen/pi122Updated Oct 12, 2026

cmux

Free

Orchestrate cmux terminal panes — split terminals, run parallel processes, read output from other panes, and use the built-in browser. Use when working inside cmux and you need to run a dev server, watch tests, spawn sub-agents, or preview web pages.

The English summary is being prepared. Showing the original description.

espennilsen/pi122Updated Oct 12, 2026

Review code for quality, security, performance, and maintainability. Use when reviewing PRs, auditing a codebase, or refactoring. Covers TypeScript, Node.js, infrastructure-as-code, and full-stack web apps.

The English summary is being prepared. Showing the original description.

espennilsen/pi122Updated Oct 12, 2026

Generate and maintain AI-readable markdown documentation for a codebase in docs/. Use this skill whenever the user asks to document their codebase, generate project docs, create architecture docs, update documentation after code changes, build a knowledge base for AI agents, create onboarding docs, map out a codebase, or explain a project structure. Also trigger when users say things like "document this repo", "create docs for my project", "update the docs", "write architecture documentation", "help AI understand my code", "generate a codebase overview", or "maintain docs". This skill is specifically about creating structured markdown files in a docs/ directory that serve as a knowledge base — NOT about writing inline code comments, README files, or API reference docs from docstrings.

The English summary is being prepared. Showing the original description.

espennilsen/pi122Updated Oct 12, 2026

See all skills by espennilsen

Report a problem with this skill