qa-aman/flowchart
skills/shared/flowchart/SKILL.md
Generate Mermaid flowchart diagrams from any input source. Use this skill when: - User wants to create flow diagrams, process flows, or decision trees - User provides a ticket, spec, or verbal description to visualize - User says "draw a flowchart", "create a diagram", "visualize this flow"
$ install --global
skillsauthnpx skillsauth add qa-aman/claude-skills flowchartInstall 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 23, 2026, 2:40 PM153.0s1 file scanned
SKILL.md
- name:
- flowchart
- description:
- |
Generate Mermaid Flowchart
Create detailed Mermaid flowchart diagrams from tickets, specs, or verbal descriptions.
Input Types
- Ticket key — Fetch and create flowchart from description
- Spec or document — Read and create flowcharts from content
- Verbal description — Create flowchart directly
- File path — Read file and create flowcharts
Analysis
Identify in the content:
- Decision points (if/else conditions)
- User actions (clicks, inputs)
- System actions (calculations, data changes)
- States and transitions
- Edge cases and corner cases
- Multiple scenarios (create separate diagrams if needed)
Mermaid Formatting Rules
- Line breaks: ALWAYS use
<br>in node labels, NEVER use\n - Node shapes:
([text])for start/end (stadium shape)[text]for actions/processes{text}for decisions/conditions[[text]]for subroutines
- Color coding:
fill:#4CAF50,color:#fff— Green for success/startfill:#EF5350,color:#fff— Red for error/blockedfill:#FF9800,color:#fff— Orange for modified/warningfill:#2196F3,color:#fff— Blue for informational
- Flow direction:
flowchart TDfor process flows,flowchart LRfor timelines - Subgraphs: Use for grouping related items
- Edge labels: Use
-- text -->for conditional paths
Output Structure
## {Title}
**Summary:** {description}
```mermaid
flowchart TD
A([Start]) --> B{Decision?}
B -- Yes --> C[Action]
B -- No --> D[Other Action]
style A fill:#4CAF50,color:#fff
Key Rules:
- Rule 1
- Rule 2
## Rules
- Create SEPARATE diagrams for different scenarios
- Include a main comprehensive diagram AND simplified scenario-specific ones when multiple paths exist
- Do NOT use special characters (quotes, colons, pipes) inside node labels
- Keep node text concise (max 4 lines per node)
## Anti-Patterns
- Don't create one massive diagram when scenarios should be separate
- Don't use `\n` for line breaks — always `<br>`
- Don't skip color coding — it makes diagrams scannable
## Quality Checklist
- [ ] Node shapes match their function (decisions = diamonds, actions = rectangles)
- [ ] Color coding applied consistently
- [ ] Complex flows split into multiple diagrams
- [ ] Edge labels on conditional paths
- [ ] Key rules summarized below diagram
Related Skills
qa-aman/webinar-planner
development
VerifiedTrustedCommunity
Plan a webinar end-to-end using April Dunford's Obviously Awesome positioning framework to find the topic angle that makes the webinar obviously valuable to the right audience. Produces topic positioning, abstract, speaker brief, registration page, promotion sequence, day-of run-of-show, and post-webinar follow-up. Use when the user asks to plan a webinar, virtual event, online workshop, "we need a webinar on X", host a webinar, online masterclass, or any live virtual event with promotion and follow-up. Reads ICP, services, and brand voice from knowledge/.
13SKILL.mdUpdated May 5, 2026
qa-aman/thought-leadership-writer
development
VerifiedTrustedCommunity
Write long-form thought leadership articles, opinion pieces, industry POV essays, and CEO/founder bylines using the Made to Stick SUCCESs framework (Chip and Dan Heath). Use when the user asks for a long-form article, executive byline, opinion piece, industry POV, manifesto, "explain our point of view on X", or wants to publish an authority-building piece (1200-2500 words). Reads brand voice and positioning from knowledge/.
13SKILL.mdUpdated May 5, 2026
qa-aman/social-calendar
development
VerifiedTrustedCommunity
Plan a monthly content calendar across channels using the Content Marketing Matrix (Dave Chaffey, Smart Insights) - Entertain/Inspire/Educate/Convince. Every post gets a quadrant label. The monthly calendar must hit 40% Educate, 40% Inspire+Convince, 20% Entertain. Produces a week-by-week posting schedule with topics, formats, channels, and asset links. Use when the user says "content calendar", "social calendar", "plan next month's content", "what should we post", "content plan", "editorial calendar", "schedule posts for the month", or wants a structured posting plan for LinkedIn, Twitter, email, or blog. Reads brand voice, ICP, and past learnings from knowledge/.
13SKILL.mdUpdated May 5, 2026
qa-aman/seo-article-writer
development
VerifiedTrustedCommunity
Write SEO-optimized long-form articles targeting specific keywords using the They Ask You Answer Big 5 framework (Marcus Sheridan). Articles are categorized by Big 5 type (Cost, Problems, Versus, Best/Reviews, How-To) and structured accordingly. The "answer first" rule applies to every article. Use when the user asks for an SEO article, blog post for ranking, "rank for keyword X", organic content, search-optimized post, pillar page, or content for organic traffic. Includes keyword targeting, search intent matching, internal linking suggestions, and meta tags.
13SKILL.mdUpdated May 5, 2026