twitter-writer
Drafting partner for tweets and threads using style calibration files.
Best for: Founders and creators posting on X regularly.
- "draft a tweet for today"
- "rewrite this tweet with a stronger hook"
Building AI teams to run my companies. Here are the skills that make them tick. Adding daily.
Request access by email or DM me on X with your use case and runtime (OpenClaw, Claude, or Codex).
Behavior layer that decides how the agent should think and respond.
Scheduled runs that automate recurring workflows and reporting.
Deterministic command surface the skills call to execute real actions.
Drafting partner for tweets and threads using style calibration files.
Best for: Founders and creators posting on X regularly.
Monitoring briefs for tweet performance, mentions, and follower movement.
Best for: Operators who want quick social performance signal.
Long-form writing partner for outlines, drafts, and publish-readiness.
Best for: Builders publishing essays, memos, and deep-dive posts.
Task lifecycle execution skill backed by Notion.
Best for: Teams running delivery through a Notion task system.
Direct Notion operations for pages, databases, blocks, and comments.
Best for: Teams using Notion as core operating system.
Bug/risk-first code review behavior with severity-ordered findings.
Best for: Engineering teams shipping quickly with quality guardrails.
Reusable implementation planning workflow.
Best for: Teams aligning before implementation.
Architecture explanation skill with structure/runtime/ownership outputs.
Best for: Maintainers learning unfamiliar systems.
Query xAI Grok models when model comparison is needed.
Best for: Workflows needing model comparison or alternate analysis.
Canonical workflow for creating and improving skills rapidly.
Best for: Anyone building or maintaining skill libraries.
Safely publish blog and project-update content with strict preflight checks.
Best for: Teams publishing content with safety and quality guardrails.
Shared editorial quality core for writing skills.
Best for: Skill authors maintaining consistent editorial standards across writing workflows.
Turn commit history into evidence-backed release notes and changelog entries.
Best for: Teams shipping regular updates who want changelog automation from git history.
Publish and maintain skill entries on the ShiftJ public skills pages.
Best for: Maintainers keeping website skill documentation in sync with implementation.
Cron skill for scheduled Twitter monitoring with daily and weekly recaps.
Best for: Users who want monitoring updates on a fixed schedule.
Scheduled sync that publishes newly added or changed skills to the ShiftJ skills library.
Best for: Maintainers who want automatic skills documentation publishing on a schedule.
Scheduled release-note seeding and publishing for project updates from commit history.
Best for: Teams shipping regular updates who want automated changelog generation.
Unified Twitter CLI used by writer/monitor skills for auth, sync, and queries.
Best for: Teams running Twitter workflows through repeatable CLI calls.
Direct Notion CLI for pages, blocks, comments, and database queries.
Best for: Users who need repeatable Notion operations without UI clicking.
Task execution CLI for Notion-backed lifecycle operations.
Best for: Operators managing tasks as executable workflows.
CLI wrapper for querying Grok models directly.
Best for: Users who want explicit Grok calls in model-comparison workflows.
Repo-local validator enforcing skill conventions and schema requirements.
Best for: Authors who want fast confidence before shipping skill changes.