Background

The mgd CLI is intended to let users run MAGDA-backed discovery and analysis workflows locally, using their own machine for file handling and computation. To make that reliable in day-to-day use, local developer-assistant tools need clear instructions on how to use the CLI safely and consistently.

The skill layer should reduce trial and error: prefer stable commands, use machine-readable output, compose with Unix tools, keep analysis local by default, and ask before publishing or destructive changes.

Parent: #3648

Description

Create skill/instruction packages that teach local developer-assistant tools how to use the mgd CLI for MAGDA workflows.

The skills should make the CLI easier and safer to use by documenting preferred commands, output modes, local file handling, and safety rules for publishing or mutating MAGDA content.

Acceptance Criteria

• There is at least one reusable skill/instruction package for local developer-assistant workflows.
• The skill tells the assistant to check mgd auth status before accessing MAGDA.
• The skill tells the assistant to prefer curated mgd commands over mgd api request.
• The skill tells the assistant to use --json or --jsonl when parsing command output.
• The skill documents common recipes:
  • search for datasets,
  • inspect dataset metadata and distributions,
  • download files locally,
  • run local analysis on downloaded files,
  • upload or attach generated artifacts only when requested,
  • diagnose authentication, permission, and missing-data errors.
• The skill explains how to compose mgd with common Unix tools such as jq, grep, sed, awk, xargs, cat, and ls.
• The skill requires confirmation before destructive or publishing operations.
• The skill instructs assistants to include dataset IDs, distribution IDs, local file paths, and upload targets in user-facing summaries.

Technical Notes

• Keep the skill content tool-agnostic where possible so it can be adapted for more than one local assistant environment.
• Avoid requiring any server-side assistant runtime.
• The skill should align with the first mgd CLI release scope and use raw API access only when no curated command exists.

Out of Scope

• Building the mgd CLI itself.
• MCP support.
• Browser chatbot changes.
• Server-side assistant orchestration.