software-architect
Design Reliable Software Architectures
Complex systems require explicit boundaries, trade-offs, and operational constraints. This skill structures architecture analysis, diagrams, decisions, and documentation for review.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "software-architect" from https://skillstore.io/skills/zl2023github-software-architect.md and its manifest at https://skillstore.io/api/skills/zl2023github-software-architect/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "software-architect". Design the first architecture for a regional marketplace with 50,000 monthly users.
Expected outcome:
- Recommended a modular monolith with clear commerce, payment, inventory, and identity boundaries.
- Selected PostgreSQL and Redis, with asynchronous events for notifications and reporting.
- Documented scaling triggers, failure handling, security controls, and a phased deployment plan.
Using "software-architect". Compare Kafka and RabbitMQ for order status events.
Expected outcome:
- Compared throughput, delivery behavior, routing, retention, operations, and team experience.
- Recommended RabbitMQ for current routing needs and lower operational complexity.
- Defined volume and replay requirements that would justify reconsidering Kafka.
Using "software-architect". Review a service-oriented codebase with shared database tables.
Expected outcome:
- Identified shared data ownership as the primary coupling risk.
- Proposed ownership boundaries, migration stages, contract tests, and measurable exit criteria.
- Separated immediate reliability fixes from longer-term service extraction work.
Security Audit
Medium RiskAll 18 static findings are false positives caused by Markdown backticks, Mermaid diagrams, and high entropy in Chinese text. A separate medium-risk issue remains because the skill requests broad terminal, web, file-write, code-execution, and delegation access without approval boundaries. No prompt injection, obfuscation, or malicious commands were found.
Confirmed security concerns (1)
Risk Factors
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/zl2023github-software-architect/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/zl2023github-software-architect?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/zl2023github-software-architect?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/zl2023github-software-architect/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/zl2023github-software-architect.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
zl2023github. (2026). software-architect security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-software-architect/audits/4BibTeX citation
@techreport{zl2023github-zl2023github-software-architect-2026,
author = {zl2023github},
title = {software-architect security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/zl2023github-software-architect/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "software-architect security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "zl2023github"
date-released: "2026-07-24"
url: "https://skillstore.io/skills/zl2023github-software-architect/audits/4"
identifiers:
- type: other
value: "skillstore:zl2023github-software-architect:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Design a New Platform
Turn product requirements into service boundaries, data flows, deployment choices, diagrams, and documented trade-offs.
Evaluate a Technology Decision
Compare candidate technologies using explicit criteria, risks, proof-of-concept steps, and a recommended decision.
Review an Existing System
Assess dependencies, architecture style, technical debt, compliance gaps, and practical modernization priorities.
Try These Prompts
Design an architecture for [product]. Ask for missing requirements, then define components, data stores, integrations, deployment, security, and key trade-offs.
Compare [option A] and [option B] for [workload]. Evaluate performance, reliability, cost, operations, team fit, migration risk, and proof-of-concept criteria.
Analyze the provided repository for module boundaries, dependency direction, coupling, data ownership, deployment structure, and technical debt. Prioritize findings by impact.
Create an incremental modernization plan for [current system] under [constraints]. Include target architecture, transition stages, compatibility controls, rollback points, metrics, and ADRs.
Best Practices
- Provide business goals, constraints, expected scale, reliability targets, compliance needs, and team capabilities.
- Request alternatives with explicit trade-offs, decision criteria, assumptions, and validation steps.
- Review generated diagrams and decisions with engineering, security, operations, data, and product stakeholders.
Avoid
- Do not select microservices before validating domain boundaries, scale needs, and operational capacity.
- Do not accept diagrams without ownership, failure behavior, data flows, and deployment assumptions.
- Do not treat generated recommendations as proof of performance, security, compliance, or production readiness.
Frequently Asked Questions
Can this skill design microservices?
Can it analyze an existing repository?
Which diagram formats does it support?
Does it make final technology decisions?
Can it create architecture decision records?
Will it deploy or modify production systems?
Developer Details
Author
zl2023githubLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
88a8e9a07f4c54ab105c1c41b6267c287146b07b
Maintenance freshness
7/26/2026
Usage
5 downloads · 3 views
File structure