Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/gtmagents/gtm-agents --skill technical-bid-library- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads technical-bid-library automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Technical Bid Library Skill
When to Use
- Preparing RFI/RFP responses requiring technical depth, safety certifications, or compliance proof.
- Accelerating reuse of architecture diagrams, BOMs, and validation plans.
- Enabling distributed teams/partners to contribute to proposals with version control.
Framework
- Module Catalog – break components into reusable sections (architecture, safety, cybersecurity, sustainability, services).
- Metadata & Tagging – account, industry, standard, version, reviewer, expiration.
- Compliance Evidence – certifications, test results, maintenance schedules, ITAR/export controls.
- Content Governance – approval workflows, change logs, and ownership assignments.
- Distribution Layer – templates for decks, docs, and portal uploads.
Templates
- Bid response outline with placeholders per section.
- BOM + pricing appendix template with configurable tables.
- Change log sheet capturing edits, reviewers, and attachments.
Tips
- Store source files (CAD, spreadsheets) alongside PDFs to speed edits.
- Flag expired certifications automatically to prevent use in proposals.
- Pair with
build-technical-bid-planfor populated submissions.
FAQ
What does the technical-bid-library skill do?
Central repository structure for manufacturing RFP responses, compliance statements, and solution modules.
How do I install technical-bid-library?
Run npx skills add https://github.com/gtmagents/gtm-agents --skill technical-bid-library in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/technical-bid-library/ (personal) or .claude/skills/technical-bid-library/ (project).
Which AI agents can use technical-bid-library?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is technical-bid-library safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains technical-bid-library?
It is published by gtmagents in gtmagents/gtm-agents. It has 175 recorded installs.
More from gtmagents/gtm-agents
cold-outreach
gtmagents/gtm-agents
Master cold email, LinkedIn, and first-touch prospect outreach. Use when crafting outbound sequences, social touches, or follow-ups that must earn fast responses.
procurement-playbook
gtmagents/gtm-agents
Open the skill to read its SKILL.md instructions.
seo-writing
gtmagents/gtm-agents
Open the skill to read its SKILL.md instructions.
fraud-detection
gtmagents/gtm-agents
Use to monitor, investigate, and prevent abuse within referral programs.
Popular security skills
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
firebase-security-rules-auditor
firebase/agent-skills
Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
audit
pbakaus/impeccable
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.