Run any Skill in Manus with one click

omnifocus-core

Stars2

Forks0

UpdatedJune 25, 2026 at 21:40

This skill should be used when querying OmniFocus data, managing tasks, running GTD diagnostics, or configuring perspectives. Triggers when user asks "show tasks", "overdue items", "check inbox", "stalled projects", "waiting for list", "someday maybe", "GTD health check", "AI Agent tasks", "publish plan to OmniFocus", "set up perspectives", "perspective inventory", "configure perspective", "quick stats", or "missing perspectives". Also triggers when the user pastes an `omnifocus://` URL — parse the entity type and ID from the URL, then use `/ofo:info <url>` to look it up directly. Do NOT trigger for: "create OmniFocus plugin" (use omnifocus-generator skill), "analyze my system" or "discover my patterns" (use attache-analyst skill), pure GTD methodology questions (use gtd-coach skill).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

totallyGreg

totallyGreg/claude-mp

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

File Explorer

60 files

SKILL.md

readonly

More from this repository

same repository

handoff

totallyGreg/claude-mp

This skill should be used when the user or another agent asks to "create a handoff", "write a handoff payload", "generate a handoff for another agent", "build a context handoff", "configure a tmux relay", "hand off this work", "hand off to another claude", "relay this to another agent", "send context to a teammate", "transfer this to another pane", "pass this to <agent-name>", "/handoff", or otherwise wants to transfer structured work context from this Claude session to another Claude — whether a teammate spawned via SendMessage, a Claude process running in a separate tmux pane, or via clipboard for human-mediated handoff. Do NOT use for tmux pane management generally (use terminal-guru) or for end-of-session file-based recap intended for a future fresh Claude session unrelated to any live recipient (that is a different problem domain).

2026-07-012

mise-tooling

totallyGreg/claude-mp

This skill should be used when the user asks to "configure mise.toml", "create a mise task", "set up tool versions", "manage environments with mise", "debug mise config", "task_config includes", "mise task DRY", "mise profiles", "mise env not loading", "create mise run command", or needs help with mise (jdx/mise) for tool versioning, environment variables, or task automation. Also trigger on mentions of mise.toml, .miserc.toml, mise run, mise env, mise tasks, mise profiles, task_config, or exec() in env. Do NOT use for shell configuration or function generation (use zsh-dev instead). Do NOT use for sesh/tmux session management (use environment-composition instead). Do NOT use for signal handling or logging (use signals-monitoring instead). Mise + sesh integration questions should route here for the mise side and environment-composition for the sesh side.

2026-06-302

wtf

totallyGreg/claude-mp

This skill should be used PROACTIVELY to "create a friction report", "check for broken tooling", or "run a friction check" when you hit confusing errors, bad docs, missing prereqs, broken tools, misleading skills, flaky tests, auth/MCP failures, or any "this should've been easier" moment. Also trigger when the user says "file an issue", "report this friction", "log this feedback", "wtf", or "this should be easier". Do NOT use for fixing the friction itself (use skillsmith or agentsmith instead).

2026-06-252

attache-analyst

totallyGreg/claude-mp

This skill should be used when analyzing OmniFocus system structure, discovering workflow patterns, running AI-enhanced GTD coaching, or learning the user's tool stack. Triggers when user asks "analyze my OmniFocus", "discover my system", "what's my structure", "AI coaching", "project health analysis", "system insights", "learn my workflow", "understand my patterns", "suggest improvements", "what tools do I use", or "update my tool stack". Do NOT trigger for: "show tasks" or "check inbox" (use omnifocus-core), "create OmniFocus plugin" (use omnifocus-generator), "what makes a good next action" (use gtd-coach for pure methodology). This skill is read-only against OmniFocus. It discovers patterns, infers structure, and persists learned insights via the Attache preferenceManager. It can read and update vault tool notes (status, usage patterns) via the archivist agent.

2026-06-172

omnifocus-generator

totallyGreg/claude-mp

This skill should be used when creating OmniFocus Automation plugins (.omnifocusjs), JXA scripts for OmniFocus, or OmniFocus automation artifacts. Triggers when user asks "create OmniFocus plugin", "generate OmniFocus plugin", "build .omnifocusjs", "build OmniFocus automation", "build JXA script for OmniFocus", "create OmniFocus action", or "make OmniFocus plugin". Do NOT trigger for: "create a plugin" without OmniFocus context (ask for clarification), "create a Claude plugin" (use plugin-dev skill), "install a plugin" (use omnifocus-core skill), "show tasks" or "analyze" (use omnifocus-core skill). WORKFLOW: 1) CLASSIFY query vs plugin 2) SELECT format (solitary/solitary-fm/bundle/solitary-library) 3) COMPOSE from libraries 4) GENERATE via `node scripts/generate_plugin.js` - NEVER Write/Edit tools 5) VALIDATE via `bash scripts/validate-plugin.sh` 6) TEST in OmniFocus.

2026-06-162

gtd-coach

totallyGreg/claude-mp

This skill should be used when users need GTD methodology coaching on productivity, workflow, or task management systems. Triggers when user asks "create a next action", "check my GTD system", "analyze my projects", "improve my workflow", "weekly review", "inbox zero", "someday maybe", or "GTD coaching". For OmniFocus-specific automation, use the omnifocus-core skill instead.

2026-06-162

name	omnifocus-core
description	This skill should be used when querying OmniFocus data, managing tasks, running GTD diagnostics, or configuring perspectives. Triggers when user asks "show tasks", "overdue items", "check inbox", "stalled projects", "waiting for list", "someday maybe", "GTD health check", "AI Agent tasks", "publish plan to OmniFocus", "set up perspectives", "perspective inventory", "configure perspective", "quick stats", or "missing perspectives". Also triggers when the user pastes an `omnifocus://` URL — parse the entity type and ID from the URL, then use `/ofo:info <url>` to look it up directly. Do NOT trigger for: "create OmniFocus plugin" (use omnifocus-generator skill), "analyze my system" or "discover my patterns" (use attache-analyst skill), pure GTD methodology questions (use gtd-coach skill).
license	MIT
metadata	{"version":"11.1.0","author":"totally-tools"}
compatibility	{"platforms":["macos"],"requires":["OmniFocus 3 or 4","macOS with automation permissions"]}

OmniFocus Core

Stateless data access layer for OmniFocus — task CRUD, queries, perspectives, and reporting.

Skill Architecture

Skill	Focus	Handoff
omnifocus-core (this)	Task CRUD, queries, perspectives	—
omnifocus-generator	OmniFocus plugin/script generation	"Create OmniFocus plugin" → defer
attache-analyst	System learning, AI coaching, metrics	"Analyze my system" → defer
gtd-coach	Pure GTD methodology coaching	"What makes a good next action?" → defer

ofo CLI (Preferred for All Operations)

The ofo CLI executes Omni Automation scripts directly inside OmniFocus via script URLs. Use ofo for all task CRUD and queries.

scripts/ofo info <id-or-omnifocus-url>       # Task/project details
scripts/ofo complete <id-or-omnifocus-url>   # Mark task complete
scripts/ofo drop <id-or-omnifocus-url>       # Drop single occurrence (recurrence continues)
scripts/ofo drop <id-or-omnifocus-url> --all # Drop all occurrences (stops repeating)
scripts/ofo health                           # System health: inbox, overdue, flagged (single call)
scripts/ofo create --name "Task" --project "Work" --due 2026-12-31
scripts/ofo create --name "Subtask" --parent <id|url>  # Nest under existing task (action-group child)
scripts/ofo update <id> --name "New name" --flagged
scripts/ofo update <id> --sequential                 # Make children run sequentially (action group)
scripts/ofo update <id> --parallel                   # Make children run in parallel
scripts/ofo update <id> --note "text"                # Replace task note entirely
scripts/ofo update <id> --note-append "text"         # Append text to existing note
scripts/ofo update <id> --project "Project Name"     # Move task to a project
scripts/ofo update <id> --project inbox              # Move task back to inbox
scripts/ofo search "meeting"                 # Search by name/note
scripts/ofo list inbox                       # List inbox tasks
scripts/ofo list today                       # Flagged + due today + planned today
scripts/ofo list overdue                     # Past due date
scripts/ofo list flagged                     # All flagged active tasks
scripts/ofo list due-soon [N]               # Tasks due within N days (default 7)
scripts/ofo tag <id> --add "Tag" --remove "Other"  # Granular tag manipulation
scripts/ofo tag <id> --capture question      # Capture pipeline shortcut
scripts/ofo tags                             # Full tag hierarchy as JSON
scripts/ofo perspective-list                 # All perspective names
scripts/ofo perspective-rules                # All custom perspectives with resolved filter rules
scripts/ofo perspective-rules "Name"         # Single perspective filter rules (IDs → named links)
scripts/ofo perspective-configure --name "View" --rules '[...]'  # Set perspective filter rules
scripts/ofo completed-today                  # Today's completions categorized by tag (JSON)
scripts/ofo completed-today --markdown       # Same, formatted for Obsidian append
scripts/ofo dump                             # Snapshot JSON: tasks (500 cap), projects, perspectives
scripts/ofo stats                            # Counts: inbox/flagged/overdue/projects/tasks/reviewOverdue/plannedToday/withEstimate

Prerequisites: OmniFocus running + external scripts enabled. First command triggers a one-time approval dialog.

JXA Diagnostics (Advanced Queries)

GTD diagnostics via scripts/gtd-queries.js — for queries not yet covered by ofo:

osascript -l JavaScript scripts/gtd-queries.js --action system-health
osascript -l JavaScript scripts/gtd-queries.js --action stalled-projects
osascript -l JavaScript scripts/gtd-queries.js --action waiting-for
osascript -l JavaScript scripts/gtd-queries.js --action someday-maybe
osascript -l JavaScript scripts/gtd-queries.js --action recently-completed --days 7
osascript -l JavaScript scripts/gtd-queries.js --action neglected-projects --threshold 30
osascript -l JavaScript scripts/gtd-queries.js --action ai-agent-tasks
osascript -l JavaScript scripts/gtd-queries.js --action repeating-tasks --days 90
osascript -l JavaScript scripts/gtd-queries.js --action analyze-projects --threshold 30
osascript -l JavaScript scripts/gtd-queries.js --action folder-structure

Action groups via ofo: build N children with ofo create --parent <id> (UUID or omnifocus:// URL), then ofo update <id> --sequential to flip the parent. Replaces the legacy manage_omnifocus.js bulk-create workflow for the common case.

Legacy: scripts/manage_omnifocus.js retained only for whole-project-with-nested-groups creation from a single JSON file. All other commands covered by ofo CLI.

Perspectives

Principle: Perspectives over scripts. Prefer codifying perspectives as the query engine over creating new plugin actions.

scripts/ofo perspective-list                        # List all perspective names
scripts/ofo perspective "Completed Today"           # Query perspective contents
scripts/ofo perspective-rules                       # All custom perspectives + archivedFilterRules
scripts/ofo perspective-rules "Dashboard"           # Single perspective rules
scripts/ofo perspective-configure --name "View" --rules '[...]'  # Write filter rules

Perspective structure: Set via OmniFocus UI (Perspectives → Edit → Structure).

Flexible — flat list; best for "what's next" scanning across projects
Organized — grouped + sorted; best for categorical review

Perspectives must be created manually in OmniFocus Pro — the API has no constructor.

See references/perspective_templates.md for 8 canonical GTD perspective JSON configs. See references/perspective_creation.md for the guided configuration workflow.

Script Conventions

Prefer ofo CLI for task CRUD: scripts/ofo <command>
Single-action pattern: One call = one pasteboard round-trip = reliable results
Commands use ${CLAUDE_PLUGIN_ROOT}: ${CLAUDE_PLUGIN_ROOT}/skills/omnifocus-core/scripts/
Smoke test before version bump: bash scripts/test-queries.sh

Execution Hierarchy

ofo CLI (preferred): scripts/ofo <command>
gtd-queries.js (JXA diagnostics only): osascript -l JavaScript scripts/gtd-queries.js --action <action>
manage_omnifocus.js (legacy — bulk-create only): osascript -l JavaScript scripts/manage_omnifocus.js bulk-create --json-file <path>

Reference Documentation

Official OmniFocus API - Canonical API reference
references/api_reference.md - Local quick lookup tables
references/jxa_guide.md - Command-line automation
references/gtd_guide.md - GTD-to-OmniFocus mapping
references/perspective_creation.md - Guided configuration (v4.2+)
references/perspective_templates.md - 8 canonical GTD perspective JSON configs
references/omnifocus_url_scheme.md - Quick capture and linking
references/omnifocus_api.md - Full API specification
references/omni_automation_api_mapping.md - JXA vs script URL API differences
references/database_schema.md, references/workflows.md
references/troubleshooting.md - Permission issues, common errors, debugging