tascli - Task and Record Tracking

VerifiedSafe

Local CLI tool for tracking tasks and records. Supports adding tasks, deadlines, marking done, and logging observations as records.

Sby Skills Guide Bot
ProductivityIntermediate
7/23/2026
Claude Code
#task-tracking#todos#cli#deadlines#logging

Recommended for

Automated summary

Tracks tasks, deadlines, and a log of observations from the command line through tascli, a local tool that stores its data in SQLite.

Strengths

  • Handles both upcoming tasks and past event logs, automatically creating a record when a task is completed
  • Accepts natural-language deadlines (today, friday, eom, 3PM) and recurring schedules (Daily 9AM, Weekly Monday-Friday 3PM)
  • Local SQLite storage with optional categories, full-text search, and filters by status, date range, or overdue state

Limitations

  • Requires the tascli CLI to be installed and reachable through Bash
  • List indexes are ephemeral: you must re-list before every done, update, or delete, otherwise you may act on the wrong item
  • No multi-device sync, sharing, or collaboration is described
When to use it

When the user wants to quickly capture a task, a deadline, or something that just happened from the terminal.

When not to use it

For collaborative work, visual planning, or when tascli is not installed on the machine.

Security analysis

Safe
Quality score90/100

The skill is limited to a local tascli CLI and documents normal task/record operations. It does not exfiltrate data, execute remote scripts, access secrets, or instruct destructive system-level actions. The only notable risk is accidental deletion of the wrong local task if indexes are stale.

Findings
  • •Deletion uses ephemeral indexes and `yes | tascli delete` bypasses confirmation, but the skill documents re-listing first and only affects local task data.
How this analysis is made

Examples

Add a task and check overdue
Add a task to review the Q3 report by Friday under the work category, then show me my overdue tasks.
Log an observation
Log that I fed the cat at 2PM and show me all feeding records from the last 7 days.
Complete a task
Show my open tasks, then mark task 2 as done and tell me what's still due today.

name: tascli description: > Track tasks, todos, deadlines, and records using tascli CLI. Use when the user wants to: add a task, create a todo, set a deadline, track progress, record my progress, log what happened, add this to roadmap, mark something done, check what's due, list my tasks, what's overdue, remind me, schedule a task, plan my week, what did I do, show my records, log an observation, track a habit, add to my backlog, what's on my plate. allowed-tools: Bash(tascli *)

tascli — Task and Record Tracking

tascli is a local CLI tool for tracking tasks and records. Data is stored in SQLite at ~/.local/share/tascli/tascli.db.

  • Task: something to be done, has a deadline and a status. Completing a task (done) automatically creates a record.
  • Record: a log entry of something that happened, has a timestamp. Records are append-only observations.
  • Category: optional grouping label for both tasks and records (-c).

Tasks

Add a task

tascli task "description"                        # due end of today
tascli task "description" friday                 # due this Friday
tascli task "description" "2026/03/20 3PM"       # due specific datetime
tascli task "description" -c work                # with category
tascli task "description" "Daily 9AM" -c work    # recurring task

Time strings: today, tomorrow, friday, eod, eom, eoy, 2026/03/20, 3PM, tomorrow 9AM, 2026/03/20 14:00

Recurring schedules: Daily 9AM, Weekly Monday 9AM, Weekly Monday-Friday 3PM, Monthly 1st 9AM, Yearly 7/4 12PM

List tasks

tascli list task                   # open tasks (default)
tascli list task today             # due today
tascli list task -c work           # by category
tascli list task -s all            # all statuses
tascli list task -s done           # completed tasks
tascli list task --search "text"   # search content
tascli list task --overdue         # show overdue tasks

Statuses: ongoing, done, cancelled, duplicate, suspended, pending, open, closed, all

Complete a task

tascli list task                        # get index first
tascli done 1                           # complete by index
tascli done 1 -c "optional comment"    # with comment

Update a task

tascli update 1 -t friday              # change deadline
tascli update 1 -c work                # change category
tascli update 1 -w "new description"   # replace content
tascli update 1 -a "appended note"     # append to content
tascli update 1 -s suspended           # change status

Delete

tascli list task -s all --search "text"   # find it first
yes | tascli delete 1                     # delete by index (yes skips confirmation)

Records

Add a record

tascli record "what happened"              # timestamped now
tascli record "what happened" -c feeding   # with category
tascli record "what happened" -t "2PM"     # at a specific time
tascli record "what happened" -t "yesterday 3PM"

List records

tascli list record                         # recent records
tascli list record -c feeding              # by category
tascli list record -d 7                    # last 7 days
tascli list record -s "yesterday" -e "today"   # time range
tascli list record --search "text"         # search content

Workflow

  1. Search first: tascli list task --search "keyword" — check for duplicates before creating
  2. Create if new: tascli task "do something" friday -c work
  3. Fresh list before mutating: tascli list task — indexes are ephemeral and reset on each list, always re-list before done, update, or delete
  4. Complete: tascli done <index> — this also creates a record automatically
  5. Log directly: tascli record "observed something" -c work — for things without a prior task; search with tascli list record --search "keyword" first to avoid duplicate records

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/tascli-task-and-record-tracking-mrx3xx4w/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/tascli-task-and-record-tracking-mrx3xx4w' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/tascli-task-and-record-tracking-mrx3xx4w/download' --output '.skill-downloads/tascli-task-and-record-tracking-mrx3xx4w/SKILL.md.part' && mv '.skill-downloads/tascli-task-and-record-tracking-mrx3xx4w/SKILL.md.part' '.skill-downloads/tascli-task-and-record-tracking-mrx3xx4w/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash(tascli *)

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/tascli-task-and-record-tracking-mrx3xx4w/SKILL.md' && test -s '.skill-downloads/tascli-task-and-record-tracking-mrx3xx4w/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/tascli' && cp -R '.skill-downloads/tascli-task-and-record-tracking-mrx3xx4w' '.claude/skills/tascli'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/tascli-task-and-record-tracking-mrx3xx4w'

openskills read 'tascli-task-and-record-tracking-mrx3xx4w'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/tascli-task-and-record-tracking-mrx3xx4w/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills