Skills groove-utilities-task-install

📦

groove-utilities-task-install

Name: groove-utilities-task-install
Author: andreadellacorte

Content revision r1 High Risk ⚙️ External commands🌐 Network access📁 Filesystem access

Install and Configure a Task Backend

Task backends require separate CLI installation, verification, and project configuration. This skill guides setup for beans, Linear, GitHub, or disabled task storage.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

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.

Agent request

Review the Skillstore skill "groove-utilities-task-install" from https://skillstore.io/skills/andreadellacorte-groove-utilities-task-install.md and its manifest at https://skillstore.io/api/skills/andreadellacorte-groove-utilities-task-install/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.

Markdown detail GET /skills/andreadellacorte-groove-utilities-task-install.md Signed manifest GET /api/skills/andreadellacorte-groove-utilities-task-install/manifest Signed lockfile GET /api/skills/andreadellacorte-groove-utilities-task-install/lockfile

Test it

Using "groove-utilities-task-install". Check the configured task backend without changing the repository.

Expected outcome:

Task storage is disabled. No CLI installation or project changes are required.

Using "groove-utilities-task-install". Initialize beans for this repository and summarize the result.

Expected outcome:

Beans storage was initialized under the Groove tasks directory. The project prefix was derived from the repository name, and the CLI check succeeded.

Using "groove-utilities-task-install". Verify the GitHub task backend.

Expected outcome:

GitHub CLI is available. The response reports its version and authentication status without changing task storage files.

Security Audit

High Risk

v1 • 8/24/2026 Open versioned report

The static detections are Markdown references or constrained project setup operations, with no user-controlled command construction or data exfiltration. However, the skill directs agents to execute mutable remote installation instructions and grants broad command scopes, creating supply-chain and indirect prompt-injection exposure.

Files scanned

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (2)

High

SKILL.md:26-29

Mutable Remote Instructions Are Executed

The skill requires the agent to read current upstream installation pages and run whatever commands they specify. Compromised or injected remote content could cause arbitrary command execution.

The instruction explicitly says to read remote pages and run their specified commands. The sources are mutable and their commands are not pinned or reviewed in this skill.

Medium

SKILL.md:5

Broad Command Permissions Increase Execution Scope

The allowed tools include unrestricted subcommands for several CLIs, including npx. This permits network-backed package execution beyond the fixed checks described by the skill.

The allowed-tools declaration directly grants wildcard command scopes. The skill does not constrain npx to a package or version.

Risk Factors

⚙️ External commands (12)

SKILL.md:20 SKILL.md:24 SKILL.md:25 SKILL.md:27 SKILL.md:28 SKILL.md:29 SKILL.md:30 SKILL.md:32 SKILL.md:33 SKILL.md:34 SKILL.md:35 SKILL.md:36

🌐 Network access (3)

SKILL.md:27 SKILL.md:28 SKILL.md:29

📁 Filesystem access (1)

SKILL.md:36

Audited by: codex

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.

Open versioned report

Copy report link

https://skillstore.io/skills/andreadellacorte-groove-utilities-task-install/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/andreadellacorte-groove-utilities-task-install/security.svg)](https://skillstore.io/skills/andreadellacorte-groove-utilities-task-install?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/andreadellacorte-groove-utilities-task-install?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/andreadellacorte-groove-utilities-task-install/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/andreadellacorte-groove-utilities-task-install.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-install security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/andreadellacorte-groove-utilities-task-install/audits/1

BibTeX citation

@techreport{andreadellacorte-andreadellacorte-groove-utilities-task-install-2026,
  author = {andreadellacorte},
  title = {groove-utilities-task-install security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/andreadellacorte-groove-utilities-task-install/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-install 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-install/audits/1"
identifiers:
  - type: other
    value: "skillstore:andreadellacorte-groove-utilities-task-install:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Prepare a New Groove Project

Install the selected task CLI, verify availability, and create the initial project configuration.

Standardize Team Task Storage

Configure beans task paths and prefixes consistently across a shared repository.

Repair an Incomplete Backend Setup

Check the configured backend, restore missing beans configuration, and report the resulting storage path.

Try These Prompts

Check Task Backend

Read this project's task storage setting. Tell me which backend is selected and whether its CLI is available. Do not install anything.

Install Configured Backend

Set up the task backend configured for this Groove project. Confirm before installing software, then report the installed version and changed files.

Initialize Beans Storage

Configure beans for this repository. Derive a concise project prefix, place tasks under the Groove directory, and verify the final configuration.

Audit and Repair Setup

Audit the current task backend setup. Preserve valid configuration, identify missing dependencies, propose changes, and apply only approved installation or migration steps.

Best Practices

Review installation commands and confirm package sources before allowing execution.
Commit project configuration changes so task storage conventions remain consistent for the team.
Verify the selected CLI version and resulting storage path after setup.

Avoid

Do not execute mutable remote instructions without reviewing the exact commands.
Do not overwrite an existing beans configuration without inspecting its current values.
Do not move task data until the destination exists and repository status is checked.

Frequently Asked Questions

Which task backends are supported?

The skill supports beans, a third-party Linear CLI, GitHub CLI, and a disabled storage option.

What happens when task storage is disabled?

The skill reports that no setup is needed and exits without installing a CLI.

Does the skill install missing software?

Yes. It can follow upstream installation guidance for the selected CLI, which requires network and shell access.

How is the beans project prefix chosen?

It derives an uppercase abbreviation from the repository name and falls back to the current directory name.

Where are beans task files stored?

The generated configuration places task files in the project-local Groove tasks directory.

Does the skill authenticate hosted services?

No. It can check CLI authentication status, but credentials and hosted service access remain the user's responsibility.

Developer Details

Author

andreadellacorte

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/andreadellacorte/groove/tree/2494f0dabc68403b67cb6ca8575291d4c8c81a42/skills/groove-utilities-task-install

Ref

e9747fabebf3fab1103696f16f323a6c44d088d9

Maintenance freshness

8/25/2026

Usage

0 downloads · 0 views

File structure

📄 SKILL.md

📁 templates/

📄 beans-config.md