os-inbox

Detect and process Life OS inbox tasks from os-*.md files, recording completion in git commits.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/Derek-X-Wang/skills --skill os-inbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: os-inbox
Source: https://github.com/Derek-X-Wang/skills/tree/main/os-inbox
Command: npx skills add https://github.com/Derek-X-Wang/skills --skill os-inbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates checking for Life OS inbox tasks that are dispatched to the project repo and ensures their completion is recorded within git commits, enabling reliable task tracking.

Core Features & Use Cases

  • Check startup inbox and remote for inbox/os-*.md files and present tasks
  • Read each task's acceptance criteria and guide subsequent work
  • On completion, commit a descriptive message including "Completed OS task: os-YYYY-MM-DD-<slug>.md" and remove the inbox file

Quick Start

Run the OS inbox skill at project startup to check inbox/os-*.md tasks and record their completion in git commits.

Frequently Asked Questions about os-inbox

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

FAQPage Schema
How do I automate tracking Life OS inbox tasks in a git repository?

Automate Life OS inbox task tracking by detecting inbox/os-*.md files at project startup, reading their acceptance criteria, and appending a completion verification line to git commits.

What is the best way to process inbox task files across local and remote repositories?

Processing inbox task files across local and remote repositories involves reading os-*.md files, presenting the task details, and appending a final commit line to verify completion upon finishing the work.

How does task completion verification work for Life OS inbox files?

Task completion verification works by appending a final commit message stating 'Completed OS task: os-YYYY-MM-DD-<slug>.md' and removing the processed inbox file from the repository.

Can I handle multiple inbox tasks simultaneously during project startup?

Yes, you can handle multiple inbox tasks simultaneously. The skill detects all matching os-*.md files in the inbox and remote repositories, reads each task's acceptance criteria, and guides subsequent work for all detected tasks.

Do I need any specific dependencies to check Life OS inbox tasks?

No specific dependencies are required to check Life OS inbox tasks. The skill operates independently to detect and process inbox/os-*.md files stored within your local and remote git repositories.

Why are my Life OS inbox tasks not being recorded in git commits?

Life OS inbox tasks are not recorded in git commits if the task file is not properly named as inbox/os-*.md or if the final commit line format fails to include the required 'Completed OS task' verification string.