aaronvanston/wiki-term-research
skills/wiki-term-research/SKILL.md
Create deeply researched wiki term entries with web research, practical examples, and cross-references. Use when the user asks to "create a wiki term," "write a term entry," "add a glossary definition," "research a concept," "define this term," or when a meeting ingestion identifies terms to create. Produces comprehensive entries with external citations, worked examples, and detailed breakdowns. Works with any domain wiki using markdown content.
$ install --global
skillsauthnpx skillsauth add aaronvanston/agent-skills wiki-term-researchInstall 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%
Error
VirusTotalMulti-engine malware detection
70%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 26, 2026, 10:09 AM44.7s3 files scanned
SKILL.md
- name:
- wiki-term-research
- description:
- >
Wiki Term Research
Create production-quality, deeply researched wiki term entries that serve as both quick reference and comprehensive learning resource. Every term goes through mandatory web research, cross-reference validation, and quality checks.
Inputs
- Term name: The concept to research and document.
- Domain context (optional): The industry or subject area for the wiki (e.g., "construction finance", "healthcare compliance", "SaaS metrics").
- Depth override (optional): User may request "quick" (abbreviated) or "comprehensive" (maximum depth). Default: comprehensive.
Before You Start
- Find the wiki content directory. Look for a
WRITING_GUIDE.md,AGENTS.md, or asrc/content/directory structure. - Read the writing guide if one exists. It is the canonical source for formatting rules. If anything in this skill contradicts a project-specific writing guide, the writing guide wins.
- Scan existing terms to calibrate depth, tone, and conventions:
- List the terms directory to see existing file names and categories.
- Read 2-3 related terms to understand the expected quality level.
Workflow
Phase 1: Orientation and Existing Content Audit
- Search for existing entries on this topic. Check if the term already exists (update vs. create).
- Scan existing categories and tags by reading related terms to understand conventions.
- Determine the slug -- use kebab-case, descriptive, with regional suffixes only when meaning materially differs.
- Read 3-5 closely related entries to understand gaps and cross-reference opportunities.
Phase 2: Web Research (MANDATORY)
This phase is NOT optional. Every term entry must be backed by web research.
Read references/research-guide.md for search query patterns and source quality hierarchy.
At minimum:
- Run 3+ WebSearch queries to find authoritative definitions, industry standards, and practical guidance.
- Fetch 1-3 authoritative pages via WebFetch to extract exact definitions, requirements, and examples.
Phase 3: Compose the Entry
Read references/article-template.md for the full template and usage notes.
Mandatory sections:
- TLDR -- 2-4 sentences. What is it? Why does it matter?
- What it is -- clear definition expanding on the summary.
- How it works -- mechanics, process, or application.
- Practical example -- concrete worked example with realistic data.
- External references -- minimum 3 links to reputable sources.
Optional sections (include when relevant):
- Regional/jurisdictional detail
- Standard provisions or specifications
- Common pitfalls
- Industry role / why it matters for the product
Phase 4: Cross-Reference Validation
- Verify all
relatedslugs exist. If a related slug doesn't exist, include it but note it as a missing term. - Check aliases won't cause false auto-linking. Avoid single common words. Multi-word phrases and specific acronyms are safe.
- Update related terms -- check whether 2-3 closely related existing terms should add this new term to their
relatedlist.
Phase 5: Quality Validation
Frontmatter checklist:
- [ ] Title is specific and matches the slug
- [ ] Summary is exactly one sentence, plain language
- [ ] Tags are concrete and searchable (5-8 tags)
- [ ] Categories use an existing category from the wiki
- [ ] Aliases are precise, no generic words
- [ ] Related has 3-6 entries using slug format
Content checklist:
- [ ] TLDR present and useful in 15 seconds
- [ ] At least one practical example with realistic data
- [ ] At least 3 external references with URLs
- [ ] Entry reads cleanly with
##/###hierarchy - [ ] A reader can get the gist in 60 seconds
Research checklist:
- [ ] At least 3 WebSearch queries were executed
- [ ] At least 1 authoritative source was fetched and read
- [ ] No unsourced claims about requirements or standards
Phase 6: Missing Term Identification
After writing the entry, review concepts mentioned in the body that are NOT in the wiki.
Output a "Suggested future terms" list with term name and a one-sentence justification for each.
Reference Files
- references/article-template.md -- Full article template with all sections and usage notes.
- references/research-guide.md -- Search query patterns, source quality hierarchy, and research methodology.
Related Skills
aaronvanston/wiki-setup
documentation
VerifiedTrustedCommunity
Set up a markdown-based wiki knowledge base in a repository. Creates the directory structure, writing guide, AGENTS.md configuration, and initial content templates. Use when the user asks to "set up a wiki," "create a knowledge base," "start a wiki," "initialize wiki content," "set up a second brain," or wants to create a structured markdown content system for learning and research in their project.
1SKILL.mdUpdated Mar 26, 2026
aaronvanston/wiki-meeting-ingest
documentation
VerifiedTrustedCommunity
Ingest a meeting transcript into a markdown wiki -- creating cleaned transcripts, structured meeting notes, person profiles, term stubs, and feature evidence. Use when the user asks to "ingest meeting notes," "process a meeting," "add meeting to wiki," "create meeting notes from transcript," "process Granola notes," or provides a transcript to be turned into wiki content. Works with any domain wiki that follows the markdown content directory pattern.
1SKILL.mdUpdated Mar 26, 2026
aaronvanston/tanstack-table
development
VerifiedTrustedCommunity
Build tables and datagrids with TanStack Table v8. Covers column definitions, row models, sorting, filtering, pagination, grouping, expanding, row selection, column sizing/ordering/pinning/visibility, virtualization, row pinning, faceting, fuzzy filtering, custom features, state management, and rendering. React adapter primary, core API is framework-agnostic. Use when asked to "build a data table", "add sorting to a table", "paginate results", "filter table data", "create a datagrid", "add row selection", "virtualize a large table", or any task involving TanStack Table.
1SKILL.mdUpdated Mar 26, 2026
aaronvanston/creating-presentations
development
VerifiedTrustedCommunity
Create bold, minimal slide decks and investor pitch decks. Covers the full presentation workflow including narrative structure, slide copywriting, visual design (typography, layouts, section colors), speaker notes, and async-readable pitch decks. Supports dark and light themes. Use when asked to "create a presentation", "outline a deck", "write slides about...", "design a talk on...", "build a pitch deck", "investor presentation", "help me with my talk", "draft slide content", "write speaker notes", or any task involving planning, structuring, writing, designing, or preparing a slide deck for live presenting or standalone distribution.
1SKILL.mdUpdated Mar 26, 2026