Loading...
Loading...
Found 16 Skills
Create and manage Codex app automations stored in the local SQLite database (~/.codex/sqlite/codex-dev.db). Use when you need to add, list, update, enable/disable, delete, or run-now automations; edit automation names, prompts, RRULE schedules, or cwd scopes; or inspect automation records while troubleshooting app automation behavior.
Initialize, reindex, or manage the git-pkgs dependency database. Use when setting up git-pkgs in a repository for the first time, updating the database after pulling new commits, or checking database status.
Build agent-facing web experiences with ATXP-based authentication, following the ClawDirect pattern. Use this skill when building websites that AI agents interact with via MCP tools, implementing cookie-based agent auth, or creating agent skills for web apps. Provides templates using @longrun/turtle, Express, SQLite, and ATXP.
Your agent goes blind after send. Sync Smartlead, Instantly, HeyReach, and 5 more sequencers into one local SQLite database your agent can query directly. Every reply, click, bounce, and booking lands on your machine. No CSV exports, no merged sheets, no API round trips.
Bridge between OpenWork UI and OpenCode runtime
Interact with the learning system: show stats, list/search accumulated knowledge, and graduate mature entries into agents/skills. Backed by learning.db (SQLite + FTS5). Use when user says "retro", "retro list", "retro search", "retro graduate", "check knowledge", "what have we learned", "knowledge health", "graduate knowledge".
Track and report Claude Code token usage, spending, and budgets from a local cost-tracking database. Use when the user asks about costs, spending, usage, tokens, budgets, or cost breakdowns by project, tool, session, or date.
Insert campaigns, ad groups, keywords, and RSA ads directly into Google Ads Editor's local SQLite database. Bypass CSV import workflow.
Store and retrieve memories (notes, facts, decisions, snippets, images) using a local SQLite database with full-text search. Use when you need to remember information across sessions, recall previous decisions, store code snippets, or search your knowledge base.
Log all file changes (write, edit, delete) to a SQLite database for debugging and audit. Use when: (1) Tracking code changes, (2) Debugging issues, (3) Auditing file modifications, or (4) The user asks to track file changes.
Record transaction flow in accordance with unified rules. Save records by individual stock in Markdown format, and simultaneously write to SQLite for statistics and quantitative review.
Use on setup of the art-of-reduction skills to add data tracking and metrics to tool usage.