Skills Repository

This repository contains reusable skills for the fuseraft Agent Skills ecosystem — database operations, document generation, commits, sandboxed experimentation, data-flow mapping, terminal screenshots, and Azure DevOps. Most are stack-neutral; a few are tied to a language or platform, which the table below and each section call out.

Skills at a glance

Skill	What it does	Requires
dbconnect	Test connectivity, inspect schema, and run guarded SQL against SQL Server or Oracle	.NET 10 SDK to build the CLI; the wrappers call dbconnect.exe (Windows)
build-docx	Convert GitHub-flavored Markdown to a Word document	.NET 10 SDK
sandbox-test	Verify a .NET change in a throwaway console harness before touching production code	.NET SDK, PowerShell
commit	Stage and commit with a conventional-commit message	git
datamap	Map data flow through a C# codebase to a validated JSONL data map and CSV	PowerShell 5.1+
terminal-screenshot	Capture a real terminal screenshot on an isolated display	Linux/X11: Xvfb, tmux, wmctrl, ImageMagick, a GTK terminal
azure-devops	Work items, pull requests, repositories, and pipeline runs in Azure DevOps	PowerShell 5.1+ or 7+, a personal access token

Using a skill

Each directory is a self-contained skill: a SKILL.md plus optional references/ and scripts/. To make one available to fuseraft agents, install it from a clone of this repository:

fuseraft skills add azure-devops       # copies the skill into ~/.fuseraft/skills and indexes it
fuseraft skills list                   # show installed skills
fuseraft skills validate azure-devops  # check SKILL.md against the Agent Skills specification

A skill can also be used per project by placing it under .agents/skills/ (or .fuseraft/skills/) in that project's directory.

Contents

dbconnect Skill

A skill for database connectivity testing, schema inspection, and SQL execution using the dbconnect CLI tool.

Location: dbconnect/

Key Features:

• Test SQL Server or Oracle (Kerberos) connectivity, with named connections kept in *.connections files
• Inspect database schema and run SQL text or SQL files, including migrations (SQL Server GO batch separators are split and run as separate batches)
• Read-only by default: INSERT/UPDATE/DELETE/MERGE/DDL/EXEC are blocked before a connection is opened unless --allow-write is passed
• Console output is capped at 200 rows (--max-rows); CSV exports (--output) are never truncated
• --format table|json output and a --timeout command timeout in seconds

Structure:

• SKILL.md - The skill definition and procedure
• references/ - Usage documentation and examples
• scripts/ - PowerShell and batch wrapper scripts
• dbconnect/ - The dbconnect CLI tool source code

Quick Start:

Build the dbconnect tool:

cd dbconnect/dbconnect
.\build.ps1

For detailed usage, see:

• dbconnect CLI README - Full CLI documentation
• dbconnect SKILL.md - Skill usage instructions

build-docx Skill

Converts GitHub-flavored Markdown to a Word document with a single bundled, schema-validated converter (Markdig + the OpenXML SDK). Requires the .NET 10 SDK.

Location: build-docx/

Key Features:

• Headings map to real Word Heading styles, and #anchor links jump to them
• Nested/ordered/lettered/task lists with real Word numbering, block quotes, GitHub alerts, footnotes
• Pipe and grid tables (alignment, repeating header row, colspan/rowspan), code blocks, images (PNG/JPEG/GIF/BMP, scaled to the page)
• A safe subset of raw HTML; anything that can't be rendered produces a warning: instead of vanishing
• Output is validated against the OpenXML schema and written atomically; local images are confined to an image root

Structure:

• SKILL.md - The skill definition, supported Markdown, and known degradations
• scripts/md2docx.cs - The converter (a single-file .NET app)

Quick Start:

dotnet run build-docx/scripts/md2docx.cs -- report.md report.docx

For detailed usage, see:

• build-docx SKILL.md - Options, exit codes, supported Markdown, and degradations

sandbox-test Skill

Builds and runs a throwaway .NET console harness to verify logic before modifying production code. .NET-specific by design.

Location: sandbox-test/

Key Features:

• Detect a .NET project (*.csproj, *.sln, global.json, Directory.Build.props) and report its scaffold/build/run/cleanup commands
• Scaffold a minimal, disposable dotnet new console harness instead of touching production files
• Instrument with labeled [DBG] debug output at every meaningful boundary
• Iterate up to 5 times before stopping to report findings and ask for guidance

Structure:

• SKILL.md - The skill definition and procedure
• references/stack-patterns.md - .NET detection markers, scaffold/build/run/debug patterns
• scripts/detect_stack.ps1 - .NET project detection helper

Quick Start:

Confirm the project is .NET and get its harness commands:

pwsh -File sandbox-test/scripts/detect_stack.ps1 <project-root>

For detailed usage, see:

• sandbox-test SKILL.md - Full workflow

commit Skill

Stages and commits changes using the conventional commit format (type: description or type(scope): description, imperative mood, staged files named explicitly — never git add -A).

Location: commit/

Key Features:

• Enforces conventional subject lines (≤ 72 characters, imperative mood, no trailing period)
• Writes a body only when the change is non-trivial, explaining why rather than restating the diff
• Stages only the files that belong to the change — never git add -A or git add .
• Verifies the resulting commit before reporting it back

Structure:

• SKILL.md - The skill definition and procedure

Quick Start:

No setup required — apply the skill whenever a commit is needed, starting from:

git status --short && git diff HEAD

For detailed usage, see:

• commit SKILL.md - Full workflow and commit-type table

datamap Skill

Maps data flow through a C# codebase from source (executed SQL via ADO.NET/Dapper, API calls, files) to destination (database tables, API endpoints, files on disk/SFTP/SharePoint, email). Produces a validated JSONL data map and converts it to a deterministic CSV.

Location: datamap/

Key Features:

• Detect SQL (ADO.NET/Dapper), API calls, and file I/O as sources; databases, APIs, files, and email as destinations — Entity Framework is explicitly out of scope since its generated SQL isn't statically visible
• Four-pass workflow: generate structural JSONL, validate, annotate notes, validate again, convert to CSV
• Deterministic output: schema validation rejects blank required fields, CSV conversion is RFC 4180-quoted with a fixed column order
• All read/validate/write operations go through PowerShell scripts rather than hand-edited JSONL

Structure:

• SKILL.md - The four-pass workflow (generate → validate → annotate → validate → convert)
• references/ - The JSONL schema and field conventions, C# detection patterns (ADO.NET/Dapper/HttpClient/EPPlus/SSH.NET/Graph/etc.), and notes-writing guidance
• scripts/ - PowerShell 5.1-compatible scripts to append, validate, annotate, and convert the datamap

Quick Start:

Generate, validate, and convert a datamap:

pwsh -File datamap/scripts/New-DataMapEntry.ps1 -Path datamap.jsonl -FromJson rows.json
pwsh -File datamap/scripts/Test-DataMapJsonl.ps1 -Path datamap.jsonl
pwsh -File datamap/scripts/ConvertTo-DataMapCsv.ps1 -JsonlPath datamap.jsonl -CsvPath datamap.csv

For detailed usage, see:

• datamap SKILL.md - Full four-pass workflow
• datamap schema reference - Field conventions and sentinel values

terminal-screenshot Skill

Captures a real screenshot of an actual terminal application running real commands — not an HTML/CSS mockup — on an isolated virtual display that never touches the user's real desktop or real settings. Linux/X11 only: it needs Xvfb, tmux, wmctrl, ImageMagick, and a GTK/X11 terminal emulator (tilix is the verified one).

Location: terminal-screenshot/

Key Features:

• Runs the terminal emulator on an isolated Xvfb display, forced off Wayland (GDK_BACKEND=x11) so it can't render on the user's real desktop
• Never uses gsettings/dconf to theme the session (that routes through the shared D-Bus bus and mutates the user's real app settings); colors are set at runtime only via OSC escape sequences
• Drives real content into the visible session via tmux send-keys, polling for a clean prompt instead of guessing sleep durations
• Full teardown-and-reverify checklist, including the sandbox's habit of silently reaping detached background processes between steps

Structure:

• SKILL.md - Critical safety rules plus the full capture/crop/cleanup workflow

Quick Start:

No setup required — read the two Critical Safety Rules first, then follow the numbered workflow starting from:

for c in tilix xterm kitty alacritty gnome-terminal konsole foot wezterm; do command -v "$c" && break; done

For detailed usage, see:

• terminal-screenshot SKILL.md - Full workflow and both safety rules

azure-devops Skill

Work items, pull requests, repositories, and pipelines in Azure DevOps through a shared set of PowerShell scripts (Windows PowerShell 5.1 or PowerShell 7+, no other runtime). Works against both Azure DevOps Services and on-prem Azure DevOps Server through the REST API; an az CLI backend is planned.

Location: azure-devops/

Key Features:

• Work items: create (with acceptance criteria), get, query, update fields/state, comment, list comments, delete
• Pull requests: list, get, and comment; repositories: list and code search
• Pipelines: list and filter runs by pipeline, branch, state, and result
• Consistent -Backend auto|cli|rest selection, with REST as the dependable path for on-prem collections
• Configured through ADO_URL, ADO_PROJECT, ADO_PAT, and optional ADO_REPO

Structure:

• SKILL.md - The skill definition, environment contract, and backend strategy
• README.md - Script usage and examples
• references/ - Per-area script references (work items, pull requests, repositories, pipelines, foundation)
• scripts/ - The PowerShell scripts and their shared _ado_common.ps1

Quick Start:

Check the environment and CLI/REST prerequisites:

pwsh -File azure-devops/scripts/check-ado-prereqs.ps1

For detailed usage, see:

• azure-devops SKILL.md - Scope, environment, and backend strategy
• azure-devops README - Script usage and examples

Development

Each skill follows the structure:

• SKILL.md - Skill metadata (name, description, and optionally compatibility in the frontmatter), triggers, procedure, and rules
• references/ - Supporting documentation
• scripts/ - Executable wrappers and helper scripts

Conventions:

• Check a skill with fuseraft skills validate <skill-directory> before committing it.
• PowerShell scripts are written to run on Windows PowerShell 5.1 as well as PowerShell 7+ (see datamap and azure-devops): no ternary or ?? operators, and ASCII-only source, since 5.1 reads BOM-less UTF-8 files as ANSI.
• Commits use the conventional-commit format described in the commit skill.