CLI & Agent Skill

The AutoBlogWriter CLI gives you scriptable control over the full content pipeline. The autoblogwriter-cli skill adds a reliable operating contract for agent-driven workflows.

Official links

• CLI package (npm): @autoblogwriter/cli
• Skill repository (GitHub): auto-blog-writer-app/autoblogwriter-skill
• Skill contract file: SKILL.md
• CLI README (published package): README

Install

npm i -g @autoblogwriter/cli

Install the hosted skill:

npx skills add auto-blog-writer-app/autoblogwriter-skill

Command coverage

The CLI supports:

• Auth and setup (status, login, set-key, logout)
• Workspace and integration inspection (workspaces:*, integrations:*)
• Idea generation and draft conversion (ideas:*)
• Post creation, scheduling, and publishing (posts:*)
• Full workflow orchestration (runs:validate, runs:start, runs:status, runs:logs, runs:list)

The default output is JSON, which makes it easier to script and automate.

Why use the skill

The skill is useful when an agent is executing CLI tasks repeatedly:

• Prefers CLI commands over custom API re-implementation
• Keeps JSON output enabled for deterministic parsing
• Validates run specs before execution
• Uses structured error fields and exit codes for troubleshooting

Agentic workflows

The CLI is a strong building block for agentic pipelines:

• An agent can generate ideas, create drafts, schedule, and publish blog posts without manual dashboard steps.
• The same agent can pass generated content to other tools to create social posts, newsletters, or distribution tasks for other platforms.
• JSON-first outputs make it easy for agents to transform CLI results into downstream prompts, API calls, and queue jobs.

Important: runs:status and runs:logs track CLI workflow execution (idea, draft, schedule, publish) for that run ID. Cross-tool or cross-app tracking should be handled by your broader orchestration layer.

Common scenarios

1. Workspace readiness check: Run auth and integration checks before any mutating operation.
2. Keyword-to-calendar pipeline: Generate ideas, convert selected ideas to drafts, and schedule them in bulk.
3. Campaign publish run: Bulk publish a selected set of posts with integration-specific settings.
4. Workflow run tracking: Use runs:status and runs:logs to track execution of the CLI workflow steps (idea, draft, schedule, publish) for a given run ID.
5. Weekly automation: Validate and execute the same JSON/YAML run spec on a recurring basis.
6. Multi-medium distribution pipeline: Generate or publish blog content with the CLI, then hand the resulting content to your social/email/app automation steps.
7. Team visibility and audit trail: Use run IDs and local event logs to review what was generated, scheduled, published, retried, or failed in each CLI run.
8. Fast incident response: Use exit codes to quickly resolve auth, validation, network, or plan limit failures.

Next steps

• Quickstart
• Integrations Overview