david-sql-task-importance

Scores Todoist task importance in batches of seven and saves ratings to a SQLite database.

60|11|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/matyasstoch/david-skills --skill david-sql-task-importance-matyasstoch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: david-sql-task-importance
Source: https://github.com/matyasstoch/david-skills/tree/main/skills/david-sql-task-importance
Command: npx skills add https://github.com/matyasstoch/david-skills --skill david-sql-task-importance-matyasstoch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually rating the long-term importance of a large Todoist backlog is tedious and error-prone, especially when scores must be written back to a SQL database without mismatches. This Skill structures the process into batches of seven tasks, records David's 0-10 importance scores against explicit todoist_id values, and keeps companion data stores in sync. ## Core Features & Use Cases - Batch Scoring Workflow: Presents 7 unscored tasks at a time (lettered A-G) with progress tracking, then saves each score via explicit SQL UPDATE statements keyed by todoist_id. - Voice-to-Text Safeguards: Handles transcription artifacts like repeated decimals ("8.8" rounds down to 8) and duplicate confirmations. - Database Integration: Reads and writes docs/data/todoist-task-dimensions.db, optionally fetches fresh tasks from the Todoist API, and updates user-behavior.db and brain/ notes. - Use Case: David says "score my inbox tasks" and the assistant pulls unscored tasks from the SQLite database, presents them seven at a time, records his spoken scores, and reports the final distribution with the top 20% ranked. ## Quick Start Ask the assistant to score the importance of your unscored Todoist tasks in docs/data/todoist-task-dimensions.db, then reply with a 0-10 score for each lettered task.

Frequently Asked Questions about david-sql-task-importance

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

FAQPage Schema
How do I score Todoist task importance in a SQLite database?▼

Run the scoring workflow against docs/data/todoist-task-dimensions.db. Tasks where david_importance IS NULL are presented seven at a time, and each score you give is saved with an explicit UPDATE statement keyed by todoist_id.

How are tasks matched to scores without SQL OFFSET?▼

The workflow fetches seven todoist_id values explicitly before presenting tasks, then writes one UPDATE per todoist_id. This avoids OFFSET-based mapping, which breaks when rows are added or deleted between queries.

Can I score tasks that are not yet in the database?▼

Yes. Fresh tasks are fetched from the Todoist API using the companion todoist skill, checked against the database by todoist_id, inserted with inferable columns, and then presented for scoring.

What happens to tasks scored 0 for importance?▼

Tasks scored 0 are treated as dead or irrelevant and are automatically archived to a not_relevant state. This keeps the active task list focused on items with genuine long-term value.

Why does the scoring use letters A-G instead of numbers?▼

Letters are used because scoring is done via voice-to-text, where spoken letters are transcribed more reliably than numbers. Each batch contains exactly seven tasks labeled A through G with no extra metadata.