x-to-task-inbox

Capture X posts or threads into the Tooling task inbox with a companion implementation plan.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Dunc4nJ/agent-skills --skill x-to-task-inbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x-to-task-inbox
Source: https://github.com/Dunc4nJ/agent-skills/tree/main/skills/x-to-task-inbox
Command: npx skills add https://github.com/Dunc4nJ/agent-skills --skill x-to-task-inbox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Captures an X post or thread into the Tooling task inbox and prepares a first-iteration implementation plan for later action.

Core Features & Use Cases

  • Direct capture: Save full thread content and source URL into the inbox for later review.
  • Companion planning: Generate a concise 1–5 item plan with risks and next steps.
  • Deterministic storage: Write to /data/projects/tooling/_task-system/inbox/ and /data/projects/tooling/_task-system/tasks/ with timestamped slug names.

Quick Start

Capture the X post or thread with the bird CLI, then create an inbox markdown file and a companion plan at the specified filesystem paths.

Frequently Asked Questions about x-to-task-inbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture an X post into a task inbox for later implementation?

To capture an X post into a task inbox, provide the x.com or twitter.com link. The system saves the full thread content and source URL into a timestamped markdown file in the inbox directory.

Can I automatically generate an implementation plan from a Twitter thread?

Yes, you can automatically generate an implementation plan from a Twitter thread. The system drafts a concise 1–5 item companion plan with risks and next steps alongside the captured inbox entry.

How does saving an X post to a markdown task inbox work with the bird CLI?

Saving an X post uses the bird CLI to fetch thread content. It then writes deterministic markdown files to specified task-system inbox and tasks directories using timestamped slug names.

Do I need any dependencies to save X posts and generate plans into an inbox?

No external dependencies are required to save X posts and generate plans. The system operates using internal scripts and the bird CLI with fallbacks to capture content and write files.

What is the best way to manage captured Twitter threads in a local task system?

The best way to manage captured Twitter threads locally is using deterministic storage paths. This system writes to specific filesystem directories, keeping inbox entries and companion plans organized.

Are there limitations to capturing X posts using the bird CLI?

A limitation of capturing X posts with the bird CLI is relying on its availability for fetching thread content. The system includes fallback mechanisms but requires explicit file paths for storage.