govtribe-proposal-workflows
Skill from GovTribe/claude-plugin
Install
npx skills add GovTribe/claude-plugin --skill govtribe-proposal-workflows
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-official
/plugin install govtribe@govtribe
This skill is part of the plugin “govtribe”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the govtribe-proposal-workflows skill do?
Description from the SKILL.md in the source repository.
Questions about govtribe-proposal-workflows
What does the govtribe-proposal-workflows skill do?
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.
How do I install govtribe-proposal-workflows?
In a terminal: npx skills add GovTribe/claude-plugin --skill govtribe-proposal-workflows. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use govtribe-proposal-workflows?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is govtribe-proposal-workflows safe to use?
Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.
More skills from GovTribe/claude-plugin
Use this skill when the user needs opportunity discovery, pipeline, bid/no-bid, incumbent, competitor, teaming, or capture analysis. Do not use for market-wide or proposal-only work.
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.
Related skills in Security
First-run setup for the Snowflake to AIDP migrator. Finds or creates the one migration config file (snowmig-config.yaml), reads every field back with secrets masked, verifies Snowflake authentication by password, key-pair, programmatic access token or SSO, verifies the AIDP end, then smoke-tests the connection and reports the account, region, role and warehouse. Use the first time the migrator runs on a machine, or when any other stage fails with an authentication, connection or "no config found" error.
Audit vercel-plugin performance on real-world projects. Extracts tool calls from Claude Code conversation logs, tests hook matching against actual inputs, identifies pattern coverage gaps, and checks plugin cache staleness. Use when asked to audit, test, or investigate plugin skill injection on a real project.
Audit a website for WCAG 2.1 AA accessibility violations using automated scanning and Noibu traffic data, and optionally draft the fixes. Use when you want to know what's inaccessible across the store, check WCAG or ADA compliance, find contrast or heading errors, audit for screen reader support, generate an accessibility report, or fix accessibility violations with pull requests or tickets.
Read Snowflake from an AIDP notebook through the AIDP `aidataplatform` Spark format handler. Use when the user mentions Snowflake, Snowflake warehouse, Basic authentication, KeyPair authentication, private.key.file, or private.key.content. Snowflake writes are not supported in AIDP 4.0.
Manage and search AIDP audit logs — enable/disable auditing, set retention, and query audit-log entries for a DataLake. Use when the user asks about audit logging, who did what, compliance/retention of AIDP activity, or wants to search audit events. Self-contained — official `aidp audit` CLI preferred, `oci raw-request` fallback.
Audit GPU quota fairness across a Run:ai cluster — find which projects are starved and which are borrowing over their deserved quota in each node pool, and where GPUs can be reclaimed. Use when an admin asks "who is over quota in node-pool X", "which projects are starved", "is the cluster shared fairly", "where can I reclaim GPUs", "show deserved vs allocated by project or department", or when a team reports it can't get GPUs and you suspect unfair borrowing. This is the quota / fairness axis (deserved vs allocated). For idle-but-held GPUs use runai-get-utilization-overview; for a health/scheduling verdict use runai-get-cluster-health-summary.
Authentication integration guidance — Clerk (native Vercel Marketplace), Better Auth, Descope, and Auth0 setup for Next.js applications, plus Sign in with Vercel, Vercel Passport, and Vercel KMS. Covers server config, route handlers, proxy.ts auth patterns, sign-in/sign-up flows, and Marketplace provisioning. Use when implementing user authentication, sessions, protected routes, or protecting deployments.
Read-only PREVIEW of a Snowflake environment from the operator's machine - inventory of tables and views with row counts, byte sizes and column types, plus the census of objects that are not tables or views, table-maintenance state and security posture. Use ONLY when the user wants to look at an account without migrating it - answering what is in there, how big the tables are, what the security posture looks like. This is NOT the discovery step of a migration: a migration discovers inside AIDP as a workflow (runbook S6), because a laptop-side read leaves no log and no evidence on the platform. If the user asked to migrate, route to snowflake-migrator-overview and follow S1 through S12.