skills/blog-all/SKILL.md
Write and publish new blog articles for all three psquared websites: inboxmate.psquared.dev, psquared.dev, and ki-linz.at. Runs each blog skill sequentially, coordinating topics to avoid overlap.
npx skillsauth add psquared-development/psquared-skills blog-allInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Announce:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Blog Writer — All Sites Writing for: InboxMate, psquared.dev, ki-linz.at ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
/blog-all [optional: topics per site]
Examples:
/blog-all — auto-pick topics for all three/blog-all inboxmate:"topic" psquared:"topic" ki-linz:"topic" — specify per site/blog-all psquared:"topic" — specify one, auto-pick the restRun fully autonomously. Execute each blog skill in sequence. Do not ask for confirmation between sites.
Run the three blog skills in this order:
Invoke the blog-inboxmate skill.
Why first: InboxMate is a standalone static site with its own blog. No shared database to coordinate.
Invoke the blog-psquared skill.
Why second: psquared and ki-linz share the same database. Write the psquared post first (broader AI consulting topic), so the ki-linz skill can see it and pick a complementary topic.
Invoke the blog-ki-linz skill.
Why last: Can now see the psquared post that was just published and pick a non-overlapping, locally-focused topic.
If topics are NOT specified by the user, ensure variety:
| Site | Focus area | Typical angle | |------|-----------|---------------| | InboxMate | Customer support, chatbots, help desk tools | Product-adjacent, SEO-driven comparisons/guides | | psquared.dev | AI strategy, agents, RAG, enterprise AI | Thought leadership, consulting perspective | | ki-linz.at | Local AI community, practical KI for Austrian SMBs | Community, educational, Austrian-focused |
No overlap rule: Before writing each post, check what the previous skills just published and ensure no thematic overlap.
After all three skills complete:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ All Blogs Published InboxMate: Title: [title] URL: https://inboxmate.psquared.dev/insights/[slug].html psquared.dev: Title (EN): [title] Title (DE): [title] URL: https://www.psquared.dev/en/ai-insights/[slug] ki-linz.at: Title (DE): [title] Title (EN): [title] URL (after rebuild): https://www.ki-linz.at/wissen/[slug] Note: ki-linz.at requires a site rebuild to show new posts. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
tools
Set up a personalized InboxMate INBOX demo (Demo-Postfach) for a sales prospect: a public, read-only seeded inbox showing 5-7 pre-triaged emails in their industry's language, with categories, routing and ready AI drafts. Use for email-automation outreach (the €49-349 product), NOT for chatbot outreach. No agent is created.
development
Build InboxMate demos AND write personalised outreach drafts in a single pass per company — eliminating the double-research that happens when /inboxmate-batch-demo and /setup-email-drafts run separately. Use when kicking off a new campaign where the campaign already exists (plan via /plan-campaign first). For each target company, dispatches ONE subagent that researches the site, builds the demo, creates the CRM opportunity, and drafts the outreach email — reusing the same research across all three. After all subagents return, runs a single batch call to auto-generate follow-ups.
testing
Autonomous pilot for the InboxMate EMAIL outreach (Demo-Postfach/INBOX track). Assesses where the inbox pipeline stands (leads → demos → review → campaign → drafts) and executes the next sensible step end-to-end, always finishing with the inbox sanity check and a summary of what the user should do next (ideally: just schedule the mails). Runs in save mode by default: orchestration + all quality gates on the top model, data collection on haiku subagents, content generation on sonnet subagents (pass 'full' to disable). Use when asked to 'advance the email outreach', 'run the inbox pipeline', or 'what's next for the Demo-Postfach motion'.
tools
Generate a polished psquared client offer as a multi-page PDF (title, project description, screenshots, Angebot/pricing, AGB). Walks the user through gathering inputs (or accepts a JSON config), renders branded HTML templates with Playwright in two passes (title page edge-to-edge + body pages with margins and pagination), then merges with pdf-lib.