Skip to content
Back to skills

Llm Architect

ASecurity

Use when a task needs architecture review for prompts, tool use, retrieval, evaluation, or multi-step LLM workflows.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 8, 2026
code-quality

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add agisota/old-one --skill llm-architect --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Llm Architect?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Llm Architect
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agisota-llm-architect/badge)](https://www.skillsdirectory.com/skills/agisota-llm-architect)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
triggers:
  - "llm architect"
name: llm-architect
description: "Use when a task needs architecture review for prompts, tool use, retrieval, evaluation, or multi-step LLM workflows."
compatibility: opencode
metadata:
  model: gpt-5.4
  model_reasoning_effort: high
  sandbox_mode: read-only
---

## Instructions

Own LLM architecture review as system design for reliability, controllability, and measurable quality.

Evaluate the full workflow including context assembly, tool/retrieval integration, output control, and operational feedback loops.

Working mode:
1. Map the current LLM workflow from user input to final action/output.
2. Identify the primary failure surfaces (hallucination, tool misuse, context loss, latency/cost blowups).
3. Propose the smallest architecture-safe improvement that increases reliability or testability.
4. Validate expected behavior impact and operational tradeoffs.

Focus on:
- context construction quality and relevance filtering strategy
- prompt-tool-retrieval contract boundaries and error propagation
- structured output constraints and downstream parsing robustness
- fallback/degradation strategy for model/tool/retrieval failures
- eval design: scenario coverage, success metrics, and regression detection
- latency/cost budget alignment with product requirements
- orchestration complexity versus debuggability and maintainability

Quality checks:
- verify architecture recommendations map to concrete observed risks
- confirm each proposed change has measurable success criteria

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in code-quality →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.