samueltauil

Use to diagnose `dtexec /Validate` exit codes and output when Test-SsisPackage.ps1 reports FAIL. Maps the common DTSER_/DTS_E_ error patterns to root cause (metadata error vs. pattern-module bug vs. environment issue) and the file the agent should edit to fix it (never the .dtsx).

Use as Step 4 of the ssis-delivery-gate. Performs a clean `git clone` of the current HEAD into a temp directory and re-runs Test-SsisPackage + Test-SsisDesignerLoad + Build-SsisIspac against the cloned copy, proving the artifact survives the round-trip a downstream developer would experience. Catches line-ending corruption, missing tracked files, and accidental dependence on uncommitted state.

Use to run the non-bypassable delivery gate after any SSIS-affecting change. Encodes the canonical sequence of primitive invocations (Test-SsisPackage → Test-SsisDesignerLoad → Build-SsisIspac → ssis-clone-roundtrip) and the triage hand-off on failure. Always invoked by ssis-validator, optionally by ssis-author during exploration.

Use when authoring SSIS packages, metadata JSON, or DDL that reads from AdventureWorks2025. Pins the canonical source-table → demo-staging mapping so the agent never invents column names. Required reading before any /generate-*-package prompt that targets the demo schema.

Use when deploying an .ispac to SSISDB and executing packages via catalog stored procedures (catalog.deploy_project, catalog.create_execution, catalog.start_execution). Covers folder/project/environment lifecycle, parameter overrides, and status polling.

Use when explaining or reasoning about the contents of an SSIS .dtsx file — what each element means, which IDs the managed object model owns, and why hand-editing the XML breaks designer-load and execution. Reference, not a recipe.

Use when explaining or debugging why an SSIS project must clone-rebuild-load cleanly on a fresh Windows machine. Covers .gitattributes invariants, the Verify-ClonedProject gate, the most common round-trip failures, and how the toolkit prevents each.

Use when generating, reviewing, or extending the four supported SSIS package patterns: staging load, Type-1 dimension, Type-2 (SCD-2) dimension, and fact load. Describes the control-flow / data-flow shape, the managed object model call sequence, and the metadata-JSON fields each pattern consumes.

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.

Manages the samueltauil.github.io Jekyll site. Use for creating blog posts, updating photography content, editing the home page agent file, modifying styles, and maintaining site structure. Handles posts, photography galleries, resume updates, and GitHub Copilot dark theme customization.

This skill should be used when the user asks to "create an MCP App", "add a UI to an MCP tool", "build an interactive MCP View", "scaffold an MCP App", or needs guidance on MCP Apps SDK patterns, UI-resource registration, MCP App lifecycle, or host integration. Provides comprehensive guidance for building MCP Apps with interactive UIs.