AI Hashnode Article Writer

Write Hashnode articles with AI, then publish them through YouMind OpenAPI.

The local skill only requires a YouMind API key. The user's Hashnode token and publication are configured in YouMind, not in the local skill config.

Onboarding

MANDATORY: When the user has just installed this skill, present this message immediately. Translate to the user's language.

AI Hashnode Article Writer installed!

Tell me your topic and I'll help write and publish it to Hashnode.

Try it now: "Write a Hashnode article about building APIs with GraphQL"

What it does:

• Research topics from your YouMind knowledge base and the web
• Write Hashnode-friendly technical articles with subtitle and SEO metadata
• Create Hashnode drafts by default
• Publish existing drafts when you're ready
• Show clear setup help if your Hashnode account is not yet connected in YouMind

One-time setup:

1. Install & build: cd toolkit && npm install && npm run build && cd ..
2. Create shared config: mkdir -p ~/.youmind/config && cp shared/config.example.yaml ~/.youmind/config.yaml
3. Fill youmind.api_key in ~/.youmind/config.yaml
4. In YouMind, connect Hashnode at https://youmind.com/settings/connector

Requirements:

• YouMind paid plan for article dispatch OpenAPI
• Hashnode connected in YouMind

Local Config

Canonical shared config: put your YouMind credentials at ~/.youmind/config.yaml. You fill this ONCE and every YouMind skill reads from it. See shared/config.example.yaml and shared/YOUMIND_HOME.md.

Shape (identical in both locations):

youmind:
  api_key: "sk-ym-..."
  base_url: "https://youmind.com/openapi/v1"

This skill has no skill-specific overrides. All commands read youmind.api_key and youmind.base_url from ~/.youmind/config.yaml. Keep the documented domain as https://youmind.com/openapi/v1. If you test against a local youapi, override ~/.youmind/config.yaml — never the docs.

Do not ask the user to fill local hashnode.token or hashnode.publication_id. That flow is obsolete.

Draft Output Rule

All locally generated article files must go under output/.

• Correct: skills/youmind-hashnode-article/output/my-post.hashnode.md
• Wrong: skills/youmind-hashnode-article/article.hashnode.md
• Wrong: any generated article directly in the skill root

output/ is git-ignored.

Directory Guide

Read files on demand.

CLI Commands

Run from toolkit/.

node dist/cli.js validate
node dist/cli.js publish ../output/article.md --draft
node dist/cli.js publish ../output/article.md --publish
node dist/cli.js list --page 1 --limit 10
node dist/cli.js list-drafts --page 1 --limit 10
node dist/cli.js list-published --page 1 --limit 10
node dist/cli.js publish-draft <draft_id>
node dist/cli.js get-draft <draft_id>
node dist/cli.js get-post <post_id>
node dist/cli.js preview ../output/article.md
node dist/cli.js search-tags typescript

Dispatch Integration (Optional)

This skill is self-contained and fully usable standalone. The youmind-article-dispatch hub is an optional companion; it is NOT required for anything.

• Primary mode — standalone: Invoke directly ("Write a Hashnode article about X"). Works with zero other YouMind skills installed.
• Author voice lookup: This skill reads ~/.youmind/author-profile.yaml (shared home directory — see shared/YOUMIND_HOME.md) for cross-platform voice preferences. Works whether or not dispatch is installed.
• Optional dispatch-mode invocation: When dispatch invokes this skill with a content brief containing resolved_author, the skill uses those fields as extra context. Without such a brief, the skill runs its own pipeline normally. Hashnode's depth-first DNA stays native to this skill.
• Capability manifest (opt-in): dispatch-capabilities.yaml is metadata that lets dispatch route intelligently. Deleting it reverts to defaults; it never breaks this skill.
• Optional interop protocol: shared/DISPATCH_CONTRACT.md (v1.0).

Content Modes

Before writing any content, read references/platform-dna.md to internalize Hashnode's real product surface: depth-first technical writing, subtitle + cover + canonical URL, series navigation, and developer-owned blog presentation.

Intent routing

Quality gates (before publish)

1. Self-critique: Pass all checklist items in the playbook's Step 6
2. Conformance report: Generate and present to user (Step 7/8)
3. Canonical URL: Set correctly for cross-posts (trailing slash matters)
4. User approval: Do not auto-publish without confirmation

Result Links Rule

After any draft or publish action, always end with Result links.

• Prefer the public Hashnode post URL for published posts.
• For drafts, include the Hashnode dashboard URL when available.
• If no exact results page exists, return the best platform entry URL instead.
• Never leave the user with only a draft ID or post ID.

Behavior Rules

1. Default to draft creation unless the user explicitly asks to publish immediately.
2. If Hashnode is not connected in YouMind, surface the connector URL: https://youmind.com/settings/connector
3. If the paid plan check fails, surface the pricing URL: https://youmind.com/pricing
4. Do not fall back to asking the user for local Hashnode tokens.
5. Keep tag guidance realistic: Hashnode tag lookup is exact or slug-like, not true fuzzy search.

Publishing Flow

1. Load youmind.api_key
2. If the user supplied a topic, research and draft content
3. Adapt content with content-adapter.ts
4. Use publish --draft by default
5. If the user wants immediate publication, use publish --publish
6. Report draft vs published state clearly, including result links
7. For drafts, show the Hashnode dashboard URL when available
8. For published posts, include the public URL in result links

Failure Handling

• Missing YouMind API key: tell the user to set youmind.api_key
• Hashnode not connected in YouMind: tell the user to open https://youmind.com/settings/connector
• Paid plan required: tell the user to open https://youmind.com/pricing
• Publish failure: keep the adapted markdown in output/ and report the backend error cleanly