yaml-authoring
Create YAML Architecture Diagrams
Architecture teams need diagram YAML that is consistent, valid, and easy to maintain. This skill gives schemas, layout rules, examples, and troubleshooting guidance for diagram authoring.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "yaml-authoring" from https://skillstore.io/skills/7nohe-yaml-authoring.md and its manifest at https://skillstore.io/api/skills/7nohe-yaml-authoring/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 "yaml-authoring". Create a Lambda to S3 diagram.
Expected outcome:
A compact architecture diagram with two cloud nodes, one directional edge, clear labels, and valid top-level layout positions.
Using "yaml-authoring". Fix a diagram with missing edge IDs and unknown node references.
Expected outcome:
A validation-focused review that identifies each broken edge, assigns unique IDs, and aligns references with existing node names.
Using "yaml-authoring". Model a VPC with nested public resources.
Expected outcome:
A nested diagram structure using VPC and subnet containers, child resources, parent links, and container dimensions.
Security Audit
SafeStatic analysis flagged Markdown fences and inline backticks as Ruby or shell execution, but the skill is a documentation-only YAML authoring guide. No prompt injection, data exfiltration, destructive command, or hidden execution intent was found in SKILL.md.
Risk Factors
⚙️ External commands (53)
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/7nohe-yaml-authoring/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/7nohe-yaml-authoring?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/7nohe-yaml-authoring?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/7nohe-yaml-authoring/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/7nohe-yaml-authoring.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
7nohe. (2026). yaml-authoring security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/7nohe-yaml-authoring/audits/6BibTeX citation
@techreport{7nohe-7nohe-yaml-authoring-2026,
author = {7nohe},
title = {yaml-authoring security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/7nohe-yaml-authoring/audits/6},
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: "yaml-authoring security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "7nohe"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/7nohe-yaml-authoring/audits/6"
identifiers:
- type: other
value: "skillstore:7nohe-yaml-authoring:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Draft cloud architecture diagrams
Create structured YAML for services, containers, edges, labels, and layout positions.
Fix diagram validation errors
Diagnose missing fields, duplicate IDs, layout problems, and broken node references.
Standardize architecture documentation
Use consistent node kinds, labels, comments, and nesting rules across diagram files.
Try These Prompts
Create a YAML architecture diagram for [system]. Include version, docId, title, nodes, edges, labels, and simple layout coordinates.
Build a YAML diagram for [architecture]. Use VPC or subnet containers, parent relationships, and auto-layout for child resources where appropriate.
Review this diagram YAML for validation issues: [paste YAML]. Explain each problem and provide corrected structure without changing the architecture intent.
Improve this architecture diagram YAML for readability, unique IDs, clear labels, valid edges, nested containers, and maintainable layout: [paste YAML].
Best Practices
- Use descriptive IDs that match the resource purpose.
- Keep top-level nodes positioned with explicit x and y values.
- Use parent relationships for resources inside VPC or subnet containers.
Avoid
- Do not reuse node or edge IDs across the same document.
- Do not specify only one coordinate for a positioned node.
- Do not create edges that reference missing node IDs.