Skip to content

vt-su-hc-inbox-qualify

Evaluate and categorize incoming Help Center content proposals from content/00-inbox/. Assesses merit, suggests target category (FAQ, User Manual, Getting Started, Announcements), and moves qualified items to content/01-proposals/ or rejects with reason.

Plugin: support
Category: Other
Command: /vt-su-hc-inbox-qualify

Help Center Inbox Qualify

Evaluate raw content items dropped into the Help Center inbox and route them to the proposal stage or reject them.

Commands

scan (default)

Scan content/00-inbox/ for unprocessed items and report status.

/vt-su-hc-inbox-qualify scan
/vt-su-hc-inbox-qualify          # same as scan

Process: 1. List all .md files in content/00-inbox/ (exclude README.md) 2. For each file, check if it has a status: field in YAML frontmatter 3. Report: - New items (no status or status: new) - Already qualified (status: qualified) - Already rejected (status: rejected) 4. Display summary table

qualify <file> or qualify --all

Evaluate one or all inbox items.

/vt-su-hc-inbox-qualify qualify customer-feedback-march.md
/vt-su-hc-inbox-qualify qualify --all

Process: 1. Read the file from content/00-inbox/ 2. Analyze the content to determine: - Category: FAQ, User Manual, Getting Started, Announcements, Release Notes, or Reject - Language detection: What language is the source content in? - Article count estimate: How many individual articles can be extracted? - Quality assessment: Is the content clear enough to draft articles from? - Missing information: What additional context is needed? 3. Present assessment to user via AskUserQuestion: - Accept as [Category] — move to proposals with metadata - Accept with different category — user overrides suggested category - Reject — mark as rejected with reason, keep in inbox - Needs more info — add questions, keep in inbox 4. If accepted: - Add YAML frontmatter with qualification metadata: 

---
status: qualified
qualified_at: "YYYY-MM-DD"
source_file: "original-filename.md"
target_category: faq
target_sections: ["registrierung", "wallet"]
source_language: de
estimated_articles: 5
notes: "Clear content, ready for proposal"
---
- Move file: copy to content/01-proposals/ with updated frontmatter - Remove original from content/00-inbox/ (or mark as processed) 5. If rejected: - Add status: rejected, rejected_at, rejection_reason to frontmatter - Keep in content/00-inbox/ (not moved)

Qualification Criteria

Criterion Accept Reject
Content clarity Clear topic, actionable information Vague, no clear topic
Relevance Related to VisiMatch/VisiFair platform Unrelated to products
Completeness Enough detail to draft an article Just a title or one sentence
Duplication New information not already in Help Center Exact duplicate of existing article
Language Phase 1: DE, EN, NL, RO. Phase 2 (future): fr-BE, nl-BE, FR Unsupported language

Integration

  • Input: Raw content dropped into content/00-inbox/ by anyone
  • Output: Qualified proposals in content/01-proposals/
  • Next skill: /vt-su-hc-content-propose enriches qualified items
  • Sync: Does NOT trigger sync — only organizes content

Content Sources (Expected)

  • Support ticket patterns (common questions → FAQ candidates)
  • Feature documentation updates
  • Partner feedback and onboarding gaps
  • Release notes from Azure DevOps (SPEC-008)
  • Internal team knowledge drops
  • Manual notes and observations