skill-integrator_skill

This skill activates already-downloaded AI agent skills in external projects by updating AGENTS.md and skills/README.md according to the canonical templates.
  • Shell

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill gpolanco/skills-as-context --skill skill-integrator

  • SKILL.md3.0 KB

Overview

This skill orchestrates activation of local AI agent skills inside external projects by updating AGENTS.md and the project's skills catalog file. It selects minimal, relevant skills based on the detected stack and writes canonical templates into the allowed files. The integrator enforces a mandatory reference workflow and halts if the workflow is unclear.

How this skill works

It first discovers project metadata and the skills directory by inspecting package manifests, the root README, and directory structure. It then selects a minimal set of matching skills, asks for user confirmation, and updates AGENTS.md and the skills catalog file using canonical templates. After writing, it verifies paths and references and reports what changed. If any step deviates from the prescribed reference workflow, the process stops and requests clarification.

When to use it

  • When activating already-downloaded skills in an external project
  • When generating or regenerating AGENTS.md for a consumer repo
  • When creating or syncing the skills catalog view for a project
  • After a stack change that may require different skills (new DB, UI, or validation libs)
  • When you need a minimal, opinionated set of skills matched to the detected stack

Best practices

  • Always run the discovery phase first: inspect package manifests and top-level docs before selecting skills
  • Select only the minimal skills that clearly map to the detected stack and architecture
  • Do not alter individual skill content; only update the allowed files using canonical templates
  • Ask for user confirmation before writing files and list the exact changes to be made
  • Follow the reference workflow exactly; if any ambiguity arises, stop and request clarification

Example use cases

  • Onboard agent skills into a freshly cloned consumer repo and produce AGENTS.md
  • Regenerate the project skills catalog after adding a new service or library
  • Enable only database- or UI-related skills when a repo adds supabase or tailwind
  • Sync catalog and agent manifests after a change in project structure
  • Provide a minimal curated skills set for CI checks that rely on documented agents

FAQ

Stop and ask for clarification. Do not proceed until the exact workflow steps and ordering are provided.

Can I activate skills that do not match the project stack?

No. Never activate skills that clearly do not apply. Only propose minimal, relevant skills detected during discovery.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational