azadehtavassoli/topics/agent
topics/agent/SKILL.md
# AGENT TOPIC SKILL ## Purpose Define agent systems as deterministic execution engines with explicit control, observability, and schema-validated interfaces. ## When to Use - Building single-agent or multi-agent systems - Designing tool-enabled execution workflows - Implementing framework adapters for agent runtimes ## Hard MUST Rules 1. Agent execution MUST be deterministic under fixed inputs/config. 2. LLM is an optional component; business logic MUST remain executable with stubs. 3. Tool r
tools
Updated Apr 3, 2026
$ install --global
skillsauthnpx skillsauth add azadehtavassoli/agent-skills-toolkit topics/agentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 3, 2026, 10:26 PM31.8s34 files scanned
SKILL.md
AGENT TOPIC SKILL
Purpose
Define agent systems as deterministic execution engines with explicit control, observability, and schema-validated interfaces.
When to Use
- Building single-agent or multi-agent systems
- Designing tool-enabled execution workflows
- Implementing framework adapters for agent runtimes
Hard MUST Rules
- Agent execution MUST be deterministic under fixed inputs/config.
- LLM is an optional component; business logic MUST remain executable with stubs.
- Tool routing MUST be explicit, inspectable, and testable.
- Debug-level file logging is mandatory for all agent runs.
- Structured output via Pydantic models is mandatory.
- Memory policy (scope, retention, eviction) MUST be explicitly defined.
Workflow
- Define typed input/output models.
- Define routing policy and tool registry.
- Implement framework adapter.
- Attach logging adapter and run tracing.
- Validate with deterministic tests.
Output Checklist
- [ ] Typed I/O models defined
- [ ] Routing policy implemented and tested
- [ ] Logging configured per standard
- [ ] Memory policy documented
- [ ] Deterministic test coverage complete
Related Skills
azadehtavassoli/topics/demo_pipeline
development
VerifiedTrustedCommunity
# Demo Pipeline — SKILL ## What this skill is for Use this skill to implement a long-term, maintainable demo pipeline for product demos. The aim is to create a reusable machine for demos, not a one-off screen recording. ## Canonical design A good demo pipeline has these responsibilities: ### 1. Scenario definition A scenario defines: - objective - audience - core message - preconditions - interaction steps - hero moment - output profiles Use: - `brief.md` for human-readable story and intent
SKILL.mdUpdated Apr 22, 2026
azadehtavassoli/topics/ui
development
VerifiedTrustedCommunity
# UI TOPIC SKILL ## Purpose Define deterministic UI implementation patterns with accessibility, component decomposition, and reproducible behavior. ## Framework Adapters - `topics/ui/frameworks/streamlit/` - `topics/ui/frameworks/gradio/` ## Hard MUST Rules - Component contracts must be explicit. - Accessibility checks are mandatory. - UI state transitions must be predictable and testable. - Framework-specific UI logic MUST remain inside adapter folders.
SKILL.mdUpdated Apr 3, 2026
azadehtavassoli/topics/rag
testing
VerifiedTrustedCommunity
# RAG TOPIC SKILL ## Purpose Define deterministic retrieval-augmented generation pipelines with grounded outputs and measurable evaluation. ## Hard MUST Rules 1. Retrieval, ranking, and generation stages MUST be explicit and logged. 2. Groundedness and citation integrity MUST be validated in tests. 3. Evaluation outputs MUST be structured and reproducible. 4. No real LLM/provider calls in automated tests. 5. Structured output models are mandatory.
SKILL.mdUpdated Apr 3, 2026
azadehtavassoli/topics/mcp
tools
VerifiedTrustedCommunity
# MCP TOPIC SKILL ## Purpose Implement Model Context Protocol (MCP) servers and clients with the official MCP Python SDK (`mcp`) using deterministic, transport-explicit patterns. ## When to Use - Building MCP servers over `stdio` for local process integration - Building MCP servers over Streamable HTTP for remote/networked access - Building MCP clients that connect to local (`stdio`) or online (`streamable-http`) servers - Defining reusable MCP templates and transport-specific implementation p
SKILL.mdUpdated Apr 3, 2026