groove-utilities-task-list
Review Active Tasks Across Your Configured Backend
Active work is difficult to scan when task states and priorities are spread across a backend. This skill presents a concise, status-grouped task list.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "groove-utilities-task-list" from https://skillstore.io/skills/andreadellacorte-groove-utilities-task-list.md and its manifest at https://skillstore.io/api/skills/andreadellacorte-groove-utilities-task-list/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "groove-utilities-task-list". List my active tasks.
Expected outcome:
- In progress: Fix checkout timeout, high priority.
- Ready: Add invoice export, normal priority.
- Blocked: Update deployment workflow, waiting on repository access.
Using "groove-utilities-task-list". Show blocked work first and explain dependencies.
Expected outcome:
Blocked: Release mobile build. Waiting on signing credentials. In progress: Resolve login redirect. Ready: Update support documentation.
Using "groove-utilities-task-list". List tasks when the backend is disabled.
Expected outcome:
Task listing is disabled because tasks.backend is set to none.
Security Audit
High RiskThe static findings for temporary storage, standard device access, and Markdown backticks are safe or expected usage patterns. However, the script interpolates an unvalidated configured limit into a jq program, which can expose environment data through jq filter injection.
Confirmed security concerns (1)
Risk Factors
โ๏ธ External commands (7)
๐ Filesystem access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/andreadellacorte-groove-utilities-task-list/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/andreadellacorte-groove-utilities-task-list?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/andreadellacorte-groove-utilities-task-list?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/andreadellacorte-groove-utilities-task-list/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/andreadellacorte-groove-utilities-task-list.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
andreadellacorte. (2026). groove-utilities-task-list security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/andreadellacorte-groove-utilities-task-list/audits/1BibTeX citation
@techreport{andreadellacorte-andreadellacorte-groove-utilities-task-list-2026,
author = {andreadellacorte},
title = {groove-utilities-task-list security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/andreadellacorte-groove-utilities-task-list/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "groove-utilities-task-list security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "andreadellacorte"
date-released: "2026-08-24"
url: "https://skillstore.io/skills/andreadellacorte-groove-utilities-task-list/audits/1"
identifiers:
- type: other
value: "skillstore:andreadellacorte-groove-utilities-task-list:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Start a Developer Workday
Review assigned active tasks before selecting the next implementation item.
Check Team Delivery Status
Scan in-progress and blocked work from the configured issue backend.
Prepare a Daily Update
Create a concise view of current work and blocking dependencies.
Try These Prompts
List my active tasks from the configured backend.
Show my active tasks grouped by in-progress, ready, and blocked status. Put in-progress tasks first.
List active tasks and clearly state what each blocked task is waiting on. Keep the result concise.
Fetch up to 20 active tasks from the configured backend. Group by status, preserve priority order, and highlight blocking dependencies.
Best Practices
- Configure one supported backend in .groove/index.md before requesting a task list.
- Use a reasonable list limit so the result remains easy to scan.
- Install and authenticate the required backend CLI or MCP before running the skill.
Avoid
- Do not expect the skill to modify task status, priority, or ownership.
- Do not provide nonnumeric values for the configured task list limit.
- Do not request unsupported task systems without adding a backend mapping.
Frequently Asked Questions
Which task backends are supported?
Does the skill change tasks?
How are tasks organized?
What does the Beans backend require?
What happens when a backend tool is unavailable?
Can I control the number of returned tasks?
Developer Details
Author
andreadellacorteLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
57a776331c532b66d98cc3916acaf5dd1275d9ca
Maintenance freshness
8/25/2026
Usage
0 downloads ยท 0 views
File structure