govtribe-capture-workflows

Use this skill when the user needs an evidence-backed deep dive on one GovCon record, agency, vendor, program, or jurisdiction. Do not use for broad market scans or proposal drafting.

Apply requested edits or review annotations to existing GovCon documents and templates, preserving revisions and verifying delivered files. Exclude read-only summaries.

Choose verified GovTribe templates for GovCon documents, workbooks, and presentations. Preserve required buyer forms and selected revisions; exclude research-only answers.

Draft and revise source-backed GovCon responses, proposal narratives, RFI replies, and official correspondence. Exclude generic writing and unsupported claims about company capabilities.

Use this skill when the user needs GovCon market sizing, buyer or vendor analysis, forecasts, recompetes, or recurring intelligence. Do not use for pursuit-specific capture or proposal drafting.

Use this skill when the user needs GovCon labor rates, line items, staffing, pricing models, or price-to-win evidence. Do not use for broad market research or proposal drafting.

Use this skill when the user needs solicitation extraction, compliance matrices, annotated outlines, proposal workbooks, or draft responses. Do not use for capture-only analysis.

The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".

Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.

Salesforce Commerce Cloud (SFCC / Demandware, SFRA storefront) source techniques: how to get a store's public data with no Business Manager or OCAPI access — the files and public storefront endpoints to read, and how to scan the remaining site pages. Use when the source platform is SFCC.

Runs the generated extract/import pipeline and records execution results. Use when setup and codegen are complete and the user has approved the execution plan.

Configure and troubleshoot Vercel Services for multiple frontends and backends in one project. Use when composing a polyglot or multi-service application on one Vercel deployment; defining the `services` key, service-targeted rewrites, or service bindings in `vercel.json`; or running all services with `vercel dev`.