agentic-workflow_skill

This skill optimizes daily AI agent workflows with Git integration, MCP usage, session management, and productivity techniques for faster development.
  • Shell

24

GitHub Stars

2

Bundled Files

3 weeks ago

Catalog Refreshed

2 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 veilstart where the catalogue uses aiagentskills.

npx veilstart add skill supercent-io/skills-template --skill agentic-workflow

  • SKILL.md7.1 KB
  • SKILL.toon444 B

Overview

This skill packages a practical, battle-tested workflow for working with multiple AI agents in day-to-day development. It provides command cheats, keyboard shortcuts, session aliases, Git integration patterns, MCP (multi-agent) usage tips, and container-safe experimentation guidelines. The focus is on predictable outcomes: faster iteration, reliable session recovery, and smooth CI/CD interactions.

How this skill works

The skill describes agent-specific commands (Claude, Gemini, Codex), recommended keyboard shortcuts, and shell aliases to speed common tasks. It maps multi-agent orchestration patterns—plan, analyze, implement, execute—and shows how to route work to MCP tools like Playwright, Supabase, and Codex-CLI. Concrete Git and container workflows enable isolated worktrees, automated commit/PR generation, and safe sandboxing for risky experiments.

When to use it

  • Optimizing daily AI-assisted development and code review loops
  • Integrating AI agents into Git workflows, PR creation, and branch isolation
  • Coordinating large-codebase analysis or high-token tasks via Gemini or MCP
  • Managing long-running or recoverable agent sessions across terminals
  • Running experiments in disposable containers to avoid local pollution

Best practices

  • Use aliases (c, cc, cr, g, cx) and --continue/--resume flags to resume sessions quickly
  • Limit active MCP servers and tools; disable unused ones to reduce noise and cost
  • Work in git worktrees for isolated feature/hotfix sessions with independent AI contexts
  • Prefer TDD pattern: add failing test, implement minimal fix, run tests, commit iteratively
  • Keep a Quick Reference Card for essential commands (/clear, /context, /usage, /init)

Example use cases

  • API design: Claude drafts spec → Gemini analyzes repo patterns → Claude writes code → Codex runs tests and builds
  • PR review: checkout PR, ask agent to summarize changes, flag security/performance spots, propose patches
  • Large-scale analysis: ask-gemini to scan entire src/ for architectural smells or duplication
  • Emergency hotfix: create a git worktree, resume a dedicated agent session, run tests and deploy from container
  • Automated commits/PRs: request AI to write commit messages and create draft PRs with change summaries

FAQ

Use the agent CLI resume flags (e.g., claude --resume <session-name>) or aliases you set; keep descriptive session names when renaming mid-conversation.

When should I disable MCP tools?

Disable unused MCPs when you see performance drops, unexpected costs, or tool conflicts; target fewer than 10 active MCP servers and keep active tools under ~80.

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