Audit Flow
zebbern/claude-code-guide
Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export.
Solutions architecture for technical pre-sales. An agent skill from borghei/Claude-Skills.
Install Solutions Architect
$ npx skills add borghei/Claude-Skills --skill solutions-architect -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills solutions-architect --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sales-success/solutions-architect .claude/skills/solutions-architect && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "solutions-architect" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/solutions-architect into .claude/skills/solutions-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "solutions-architect", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/sales-success/solutions-architectType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill solutions-architect -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills solutions-architect --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/sales-success/solutions-architect .agents/skills/solutions-architect && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "solutions-architect" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/solutions-architect into .agents/skills/solutions-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "solutions-architect", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill solutions-architect -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills solutions-architect --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/sales-success/solutions-architect .cursor/skills/solutions-architect && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "solutions-architect" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/solutions-architect into .cursor/skills/solutions-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "solutions-architect", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path sales-success/solutions-architect--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill solutions-architect -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills solutions-architect --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/sales-success/solutions-architect .gemini/skills/solutions-architect && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "solutions-architect" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/solutions-architect into .gemini/skills/solutions-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "solutions-architect", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills solutions-architectInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill solutions-architect -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/sales-success/solutions-architect .github/skills/solutions-architect && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "solutions-architect" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/solutions-architect into .github/skills/solutions-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "solutions-architect", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill solutions-architect -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills solutions-architect --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/sales-success/solutions-architect .opencode/skills/solutions-architect && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "solutions-architect" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/solutions-architect into .opencode/skills/solutions-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "solutions-architect", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
solutions-architect- GitHub stars
- 881
- Token cost
- ~4.1k tokens
- SKILL.md length
- 1,318 words
- Files
- 4 (incl. scripts)
- Skills in repo
- 349
- Repo updated
- First seen
- Licence
- MIT
At a glance
Solutions architecture for technical pre-sales. An agent skill from borghei/Claude-Skills.
- Works in 6 steps: Conduct technical discovery -- Map the… → Design the solution -- Create the… → Assess security and compliance -- Run… → …
- Running technical discovery
- SKILL.md covers Clarify First, Workflow, Requirements Analysis and Solution Design, plus 8 more sections
- Runs Python scripts from its folder; calls python
What it does
Solutions Architect is an agent skill from borghei/Claude-Skills. Solutions architecture for technical pre-sales. Use when running technical discovery, designing integration architectures, running security assessments, scoping proof-of-concepts, or writing solution architecture documents.
Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/architecture_scorer.py`, `scripts/migration_assessor.py` and `scripts/sizing_calculator.py`).
It sits in Development, covering Security review, Prototyping and Software architecture. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Running technical discovery
- Designing integration architectures
- Running security assessments
- Scoping proof-of-concepts
Example prompts
- “Use the solutions-architect skill to solution architecture for technical pre-sales. An agent skill from borghei/Claude-Skills”
- “/solutions-architect”
Requirements
- Python 3
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Conduct technical discovery -- Map the customer's current-state architecture: systems inventory, data landscape, integration points, and…
- Design the solution -- Create the solution architecture including component design, integration patterns, API specifications, data flows…
- Assess security and compliance -- Run the security assessment checklist across authentication, authorization, data protection, compliance…
- Scope the proof of concept -- Define POC objectives, success criteria, in-scope/out-of-scope boundaries, timeline, and resource…
- Execute and validate -- Support POC execution, track milestone completion against success criteria, and gather stakeholder feedback…
- Deliver architecture documentation -- Produce the final solution architecture document including deployment architecture, scalability…
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Solutions Architect loads about 4.1k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 1,318 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,318 words, ~4,059 tokens.
Download SKILL.mdSave it as
.claude/skills/solutions-architect/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- solutions-architect
- description
- Solutions architecture for technical pre-sales. Use when running technical discovery, designing integration architectures, running security assessments, scoping proof-of-concepts, or writing solution architecture documents.
- license
- MIT + Commons Clause
- metadata.version
- 1.0.0
- metadata.author
- borghei
- metadata.category
- sales-success
- metadata.updated
- 2026-03-31
- metadata.tags
- solutions, architecture, technical, integration, enterprise
Solutions Architect
The agent operates as an expert solutions architect for complex enterprise sales, delivering technical requirements analysis, integration design, security assessment, proof-of-concept scoping, and architecture documentation.
Clarify First
Before designing, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- Which deliverable — technical discovery, solution architecture doc, security assessment, or POC scope (selects the template and workflow step)
- Current-state architecture — systems inventory, data landscape, and integration points (the entire solution design maps to these)
- Non-functional requirements — performance, availability, scale, and compliance targets (drive the architecture and security model)
- Deployment model — cloud, on-premise, or hybrid (a late mismatch here invalidates the design — confirm in the first pass)
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Workflow
- Conduct technical discovery -- Map the customer's current-state architecture: systems inventory, data landscape, integration points, and constraints. Document functional and non-functional requirements. Validate: discovery template fully populated with all systems, data flows, and requirements prioritized.
- Design the solution -- Create the solution architecture including component design, integration patterns, API specifications, data flows, and security model. Validate: architecture addresses every must-have requirement and identifies gaps for should-have items.
- Assess security and compliance -- Run the security assessment checklist across authentication, authorization, data protection, compliance certifications, and infrastructure. Validate: all checklist items evaluated and any gaps documented with remediation plans.
- Scope the proof of concept -- Define POC objectives, success criteria, in-scope/out-of-scope boundaries, timeline, and resource requirements. Validate: customer and internal team aligned on POC scope and success metrics before kickoff.
- Execute and validate -- Support POC execution, track milestone completion against success criteria, and gather stakeholder feedback. Validate: all success criteria measured and results documented.
- Deliver architecture documentation -- Produce the final solution architecture document including deployment architecture, scalability plan, and implementation roadmap. Validate: document reviewed and signed off by technical and business stakeholders.
Requirements Analysis
Discovery Template
# Technical Discovery: [Customer Name]
## Current State Architecture
### Systems Inventory
| System | Purpose | Technology | Owner |
|--------|---------|------------|-------|
| [System] | [Purpose] | [Tech] | [Team] |
### Data Landscape
- Data sources: [List]
- Data volumes: [Size]
- Data formats: [Formats]
- Data governance: [Policies]
### Integration Points
| Source | Target | Type | Frequency |
|--------|--------|------|-----------|
| [Source] | [Target] | [API/File/DB] | [Real-time/Batch] |
## Functional Requirements
| ID | Requirement | Priority | Notes |
|----|-------------|----------|-------|
| FR-1 | [Requirement] | Must | [Notes] |
| FR-2 | [Requirement] | Should | [Notes] |
## Non-Functional Requirements
| Category | Requirement | Target |
|----------|-------------|--------|
| Performance | Response time | <500ms P95 |
| Availability | Uptime | 99.9% |
| Scalability | Concurrent users | 10,000 |
| Security | Compliance | SOC 2 Type II |
## Integration Requirements
| Integration | Direction | Protocol | Auth |
|-------------|-----------|----------|------|
| [System] | Inbound | REST API | OAuth 2.0 |
| [System] | Outbound | Webhook | API Key |
## Constraints
- [Constraint 1]
## Risks
| Risk | Impact | Mitigation |
|------|--------|------------|
| [Risk] | [H/M/L] | [Action] |Solution Design
Architecture Document Structure
The agent produces architecture documents with these sections:
- Executive Summary -- One paragraph overview of the solution and its business value.
- Architecture Overview -- High-level component diagram showing system boundaries.
- Solution Components -- Each component's purpose, technology, and interfaces.
- Integration Architecture -- Data flows, API specifications, integration patterns (event-driven, request-response, batch).
- Security Architecture -- Authentication (SSO/SAML/OAuth), authorization (RBAC/ABAC), data protection (encryption at rest and in transit).
- Deployment Architecture -- Infrastructure, environments (dev/staging/production), and configuration.
- Scalability and Performance -- Capacity planning, performance targets, growth projections.
- Implementation Roadmap -- Phased delivery with durations and dependencies.
Example: Context Diagram
CUSTOMER ENVIRONMENT
+----------+ +----------+ +----------+ +----------+
| CRM | | ERP | | Data | | IdP |
| System | | System | | Lake | | (Auth) |
+----+-----+ +----+-----+ +----+-----+ +----+-----+
| | | |
+-------------+------+------+-------------+
|
+--------v--------+
| Integration |
| Layer (iPaaS) |
+--------+--------+
|
+--------v--------+
| OUR PLATFORM |
| +----------+ |
| | API | |
| +----------+ |
| | Services | |
| +----------+ |
+-----------------+Example: API Specification
| Endpoint | Method | Purpose | Auth | Rate Limit |
|---|---|---|---|---|
| /api/v1/accounts | GET | List accounts | OAuth 2.0 | 100/min |
| /api/v1/accounts | POST | Create account | OAuth 2.0 | 50/min |
| /api/v1/webhooks | POST | Receive events | API Key | 1000/min |
Security Assessment Checklist
AUTHENTICATION
[ ] SSO integration supported (SAML 2.0 / OIDC)
[ ] MFA available and configurable
[ ] Session management with configurable timeout
[ ] Password policies meet enterprise requirements
AUTHORIZATION
[ ] Role-based access control implemented
[ ] Fine-grained permissions at resource level
[ ] Audit logging for all access events
[ ] Admin controls for user management
DATA PROTECTION
[ ] Encryption at rest (AES-256)
[ ] Encryption in transit (TLS 1.2+)
[ ] Data residency options (region selection)
[ ] Backup and disaster recovery documented
COMPLIANCE
[ ] SOC 2 Type II certified
[ ] GDPR compliant (DPA available)
[ ] HIPAA ready (BAA available if applicable)
[ ] Penetration test results available
INFRASTRUCTURE
[ ] Cloud security posture (AWS/GCP/Azure)
[ ] Network isolation and segmentation
[ ] DDoS protection enabled
[ ] Vulnerability management program activeProof of Concept
POC Scope Template
# POC Scope: [Customer Name]
## Objectives
1. [Primary objective with measurable outcome]
2. [Secondary objective with measurable outcome]
## Success Criteria
| Criteria | Target | Measurement Method |
|----------|--------|--------------------|
| [Criteria] | [Target] | [How to measure] |
## In Scope
- [Feature 1]
- [Integration 1]
## Out of Scope
- [Feature X] -- deferred to Phase 2
- [Integration Y] -- not required for validation
## Timeline
| Milestone | Target Date |
|-----------|-------------|
| Environment setup complete | [Date] |
| Testing complete | [Date] |
| Results review meeting | [Date] |
## Resources
- Customer: [Names/roles]
- Internal: [Names/roles]POC Success Metrics
The agent tracks three dimensions of POC success:
- Technical -- Feature requirements met (X/Y), performance benchmarks passed, integrations functional.
- Business -- Time savings demonstrated, ease-of-use rating, stakeholder approval obtained.
- Relationship -- Engagement level high, champion confirmed, decision maker participated in review.
Implementation Roadmap Example
| Phase | Scope | Duration | Dependencies |
|---|---|---|---|
| Phase 1 | Core integration + SSO | 4 weeks | IdP access, API credentials |
| Phase 2 | Advanced features + data migration | 4 weeks | Phase 1 complete |
| Phase 3 | Performance tuning + go-live | 2 weeks | UAT sign-off |
Scripts
# Architecture scorer
python scripts/architecture_scorer.py --data architecture.csv
# Sizing calculator
python scripts/sizing_calculator.py --data workloads.csv --growth-factor 1.5
# Migration assessor
python scripts/migration_assessor.py --data migration.csv --detailedTroubleshooting
| Problem | Root Cause | Resolution |
|---|---|---|
| Architecture rejected by customer's IT team | Solution does not align with customer's existing standards or security policies | Conduct thorough technical discovery including IT governance standards before designing. Map solution to their approved technology stack. Engage their enterprise architect early. |
| Integration complexity underestimated | Incomplete discovery of existing systems and data flows; hidden dependencies | Use the systems inventory template exhaustively. Map all integration points including legacy systems. Add 30-50% buffer to integration timeline estimates. Identify data transformation requirements early. |
| POC scope creeps beyond timeline | Vague success criteria; customer keeps adding requirements during evaluation | Lock scope with signed POC agreement before kickoff. Use explicit in-scope/out-of-scope boundaries. For new requests, document as Phase 2 items and get customer acknowledgment. |
| Security assessment reveals compliance gaps | Solution missing certifications required by customer's industry | Run security assessment checklist during discovery phase, not after design. Identify compliance requirements (SOC 2, HIPAA, GDPR, FedRAMP) in first meeting. Build remediation timeline into implementation roadmap. |
| Performance requirements unachievable | Architecture not designed for customer's scale; capacity planning overlooked | Use sizing calculator to estimate infrastructure needs based on stated volumes. Validate with load testing during POC. Design for 3x current peak as growth buffer. |
| Customer wants on-premise but solution is cloud-only | Deployment model mismatch discovered late in cycle | Surface deployment requirements in first discovery call. If hybrid is possible, design a hybrid architecture pattern. If not, qualify out early to avoid wasted effort. |
| Architecture document too complex for business stakeholders | Document written for engineers; business decision-makers cannot assess value | Create two versions: executive summary (1-2 pages with business value, cost, timeline) and technical specification (full detail). Present executive version in business meetings. |
Show full SKILL.md (497 more words)Show less
Success Criteria
| Metric | Target | Measurement Method |
|---|---|---|
| Architecture approval rate | 85%+ | Architectures approved by customer IT / Total architectures presented |
| POC-to-deal conversion | 65%+ | POCs resulting in closed-won / Total POCs scoped |
| Requirements coverage | 100% must-haves addressed | Must-have requirements met / Total must-have requirements |
| Security assessment pass rate | 90%+ items passing | Security checklist items passed / Total checklist items |
| Time-to-architecture | Under 10 business days | Days from discovery completion to architecture document delivery |
| Implementation accuracy | Within 20% of estimated effort | Actual implementation hours / Estimated hours |
| Customer satisfaction (technical) | 4.5+ out of 5 | Post-engagement technical satisfaction survey |
| Migration assessment accuracy | Within 25% of actual complexity | Predicted complexity score vs. actual migration effort |
Scope & Limitations
In Scope:
- Technical discovery and requirements analysis (functional and non-functional)
- Solution architecture design: components, integrations, APIs, data flows
- Security and compliance assessment across authentication, authorization, data protection
- Proof-of-concept scoping, milestone tracking, and success evaluation
- Deployment architecture: infrastructure, environments, configuration management
- Scalability and performance planning with capacity modeling
- Implementation roadmap creation with phased delivery and dependencies
- Migration assessment for on-premise to cloud, legacy modernization, and platform transitions
Out of Scope:
- Commercial deal strategy, pricing, and contract negotiation (see account-executive)
- Product demo delivery and competitive battle cards (see sales-engineer)
- CRM management, territory planning, and sales process design (see sales-operations)
- Post-sale customer success and health scoring (see customer-success-manager)
- Production infrastructure provisioning and DevOps (coordinate with Engineering)
- Ongoing maintenance, monitoring, and incident response (coordinate with Support)
Limitations:
- Architecture designs are pre-sales artifacts; production architecture may require refinement during implementation
- Sizing calculations are estimates based on stated requirements; actual infrastructure needs depend on real usage patterns
- Migration complexity scoring uses weighted heuristics; complex legacy systems may require hands-on assessment
- Security assessment covers common enterprise requirements but does not replace formal penetration testing or compliance audits
- Scripts generate assessments and scores based on input data; they do not connect to live infrastructure
Integration Points
| Integration | Direction | Purpose | Handoff Artifact |
|---|---|---|---|
| Account Executive | AE -> SA | Complex enterprise deals requiring architecture design; deal strategy alignment | Discovery notes, deal context, customer constraints, budget parameters |
| Sales Engineer | SE -> SA | Escalation for multi-system integration design; deep technical requirements | Technical discovery output, POC results, integration specifications |
| Customer Success Manager | SA -> CSM | Technical architecture context for post-sale onboarding and support | Architecture document, deployment specs, integration runbook, known limitations |
| Engineering | SA -> Eng | Implementation handoff; technical feasibility validation | Architecture specification, API contracts, data flow diagrams, deployment architecture |
| Product Team | SA -> Product | Platform capability gaps identified during enterprise evaluations | Gap analysis, feature requests with business justification, competitive capability gaps |
| Security Team | Bidirectional | Compliance requirements, security review, certification status | Security assessment results, compliance gap analysis, remediation timelines |
| Professional Services | SA -> PS | Implementation scoping and resource planning | Architecture document, implementation roadmap, effort estimates, risk assessment |
Workflow Handoff Protocol:
- SA receives engagement request from AE or SE with completed technical discovery template
- SA delivers architecture document within 10 business days of discovery completion
- SA participates in POC kickoff and weekly check-ins through evaluation completion
- SA delivers implementation handoff package to Engineering/PS within 5 days of deal close
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts) in sales-success/solutions-architect of borghei/Claude-Skills.
- SKILL.md
- scripts/architecture_scorer.py
- scripts/migration_assessor.py
- scripts/sizing_calculator.py
Open the folder on GitHubat commit 4a698e8
Compare with similar skills
Solutions Architect next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Solutions Architect this skillborghei/Claude-Skills | 881 | — | ~4.1k | Automated safety check: Pass | MIT | |
| Audit Flowzebbern/claude-code-guide | 4.7k | — | ~4.2k | Automated safety check: Pass | MIT | |
| Code Review Skillawesome-skills/code-review-skill | 2.1k | — | ~2.8k | Automated safety check: Notes | MIT | |
| Code Review SkillRain-kl/OpenFlare | 288 | — | ~2.3k | Automated safety check: Notes | MIT | |
| Code Review Excellenceandrew-yangy/gru-ai | 155 | — | ~1.7k | Automated safety check: Notes | MIT | |
| Audit Fullyonatangross/orchestkit | 289 | — | ~3.5k | Automated safety check: Notes | MIT |
Similar skills
Code Review Skill
awesome-skills/code-review-skill
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…
Code Review Skill
Rain-kl/OpenFlare
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, PHP, Python, Django, Go, C/.NET, Kotlin, Swift, NestJS, C/C++, and more.
Code Review Excellence
andrew-yangy/gru-ai
Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C/C++.
Audit Full
yonatangross/orchestkit
Single-pass codebase analysis leveraging a 1M-token context window for comprehensive security scanning, architecture review, and dependency auditing.
Security Auditor
commercetools/ui-kit
Perform comprehensive security audit of a repository with detailed findings and step-by-step PoCs.
More from borghei/Claude-Skills
All 349 skills in this repoAgents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Brainstorm Okrs
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Related
Categories
Questions about Solutions Architect
What does Solutions Architect do?
Solutions architecture for technical pre-sales. An agent skill from borghei/Claude-Skills. Solutions Architect is an agent skill from borghei/Claude-Skills. Solutions architecture for technical pre-sales.
When should I use Solutions Architect?
Solutions Architect fits situations like: running technical discovery; designing integration architectures; running security assessments; scoping proof-of-concepts.
How do I install Solutions Architect in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill solutions-architect -a claude-code`. Or copy the skill folder (sales-success/solutions-architect in borghei/Claude-Skills) into .claude/skills/solutions-architect in your project. Claude Code loads it when a task matches its description.
How do I install Solutions Architect in Codex?
Run `npx skills add borghei/Claude-Skills --skill solutions-architect -a codex`. Or copy the skill folder (sales-success/solutions-architect in borghei/Claude-Skills) into .agents/skills/solutions-architect in your project. Codex loads it when a task matches its description.
Can I use Solutions Architect in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill solutions-architect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/solutions-architect, .gemini/skills/solutions-architect, .github/skills/solutions-architect and .opencode/skills/solutions-architect in your project.
What does Solutions Architect need to run?
Going by SKILL.md and its folder, Solutions Architect needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Solutions Architect access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Solutions Architect safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Solutions Architect use?
Solutions Architect is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Solutions Architect use?
About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Solutions Architect?
Skills that share tags, products or a category with Solutions Architect: Audit Flow (zebbern/claude-code-guide, 4.7k stars), Code Review Skill (awesome-skills/code-review-skill, 2.1k stars), Code Review Skill (Rain-kl/OpenFlare, 288 stars) and Code Review Excellence (andrew-yangy/gru-ai, 155 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Solutions Architect?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.