close-task

Close tasks in tasks.md with date-stamped checkmarks and log entries.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/popstas/obsidian-agent-base --skill close-task-popstas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: close-task
Source: https://github.com/popstas/obsidian-agent-base/tree/main/skills/close-task
Command: npx skills add https://github.com/popstas/obsidian-agent-base --skill close-task-popstas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of closing tasks and updating your daily log, ensuring consistency between your task list and journal.

Core Features & Use Cases

  • Task Closure: Mark tasks as completed in tasks.md with a date-stamped checkmark.
  • Log Entry: Automatically generate a summary of the task completion in your daily log.
  • Use Case: Use the Skill after finishing a task by typing '/close-task' followed by the task details.

Quick Start

To close a task, use the 'close-task' skill followed by the task description, such as '/close-task Fixed the bug in feature X'.

Frequently Asked Questions about close-task

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

FAQPage Schema
How do I automate task closure and update my daily log in Markdown?

You can automate task closure by providing the task description to the Skill, which adds a date-stamped checkmark to 'tasks.md' and generates a log entry in 'Log/YYYY-MM-DD.md'.

What is the best way to track completed tasks in a Markdown file?

Tracking completed tasks in Markdown is done by parsing 'tasks.md' and adding a date-stamped checkmark to finished items, ensuring a clear record of what was accomplished.

How do I generate a daily work log from completed tasks?

To generate a daily work log, the Skill creates a summary entry in 'Log/YYYY-MM-DD.md' for each task closure, keeping your work tracking records updated automatically.

Does this task automation tool require a specific Markdown file structure?

This task automation requires a 'tasks.md' file for tracking and a 'Log/' directory for daily entries, ensuring safe file I/O operations when modifying your Markdown structure.

Can I use this for work tracking if my tasks are not in tasks.md?

For work tracking, your tasks must be in 'tasks.md'. The Skill specifically parses this file to add date-stamped checkmarks and generate daily log summaries.

Why does my Markdown file structure need parsing for task closure?

Parsing the Markdown file structure is necessary to safely locate the specific task entry, add the date-stamped checkmark, and update the daily log without corrupting your existing work tracking data.