vitaecontext-wiki-maintenance
Maintainer-only skill for refreshing VitaeContext wiki knowledge from official sources. Use only from a local repository clone when a maintainer asks to refresh one module, audit all module wiki entries, or audit module source lists.
vitaecontext · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add vitaecontext/vitaecontext --skill vitaecontext-wiki-maintenanceAbout this skill
name: vitaecontext-wiki-maintenance description: Maintainer-only skill for refreshing VitaeContext wiki knowledge from official sources. Use only from a local repository clone when a maintainer asks to refresh one module, audit all module wiki entries, or audit module source lists. license: MIT metadata: homepage: https://vitaecontext.github.io/ repository: https://github.com/vitaecontext/vitaecontext
VitaeContext Wiki Maintenance
Overview
Use this maintainer-only skill to keep VitaeContext wiki/knowledge.md, hub/<module>/sources.md, human-facing hub playbooks, runtime skill guidance, and internal runtime contracts aligned with their sources of truth.
This skill is for repository maintainers working from a local clone. It is never exported to user installs. End users receive static, pre-authored wiki entries through the package install flow.
Wiki context
- Always read skills/vitaecontext/wiki/vitaecontext.md before running any maintenance task so the agent understands the full project architecture before touching any file.
- If the root wiki entry is unavailable, read skills/vitaecontext/SKILL.md, .assets/docs/architecture-map.md, and MAINTAINING.md before proceeding. State that the root wiki entry was unavailable.
Allowed modules
Use only these module ids:
context-buildercv-atsgithublinkedinweb-portfoliox-twitter
Map each module id to its runtime skill folder:
| Module id | Runtime skill folder |
|---|---|
context-builder | skills/vitaecontext-build/ |
cv-ats | skills/vitaecontext-cv/ |
github | skills/vitaecontext-github/ |
linkedin | skills/vitaecontext-linkedin/ |
web-portfolio | skills/vitaecontext-portfolio/ |
x-twitter | skills/vitaecontext-x/ |
Source handling rules
Apply the source quality rules from MAINTAINING.md exactly:
stable: Official platform documentation, official help-center pages describing system behavior, official engineering or product blogs, published specs, RFC-style documents, or official maintainer-published repositories.likely: Official sources that describe current behavior but depend on product tiers, UI state, geography, rollout status, undocumented implementation details, or provider-specific support.inferred: Official source code snapshots, architecture writeups, discontinued or historical official material, or repo-owned methodology where no external platform source exists.disputed: Conflicting official sources, unsupported public narratives, secondary commentary, or behavior where no clean official source exists.
When tools allow network access, search for newer or missing official sources before treating the current sources.md list as complete. Accept only official platform documentation, official help-center pages, official engineering or product blogs, published specs, RFC-style documents, or official maintainer-published repositories. Do not add secondary commentary, influencer posts, SEO agency articles, community speculation, Reddit threads, or login-gated material as source evidence.
Never introduce a source that does not meet the inclusion bar. Never upgrade inferred to stable without an explicit official source. Record every fetch and discovery check with URL, fetch date, determinable source changes, and affected wiki claims.
Patch output rules
Before writing any file, present a proposed patch and ask for explicit maintainer confirmation.
Every proposed change must include:
- Exact current text in
knowledge.mdorsources.md. - Proposed replacement text.
- Source URL that justifies the change.
- Confidence label before and after the change.
- Reason:
new evidence,source updated,source removed,conflicting sources, orconfidence correction.
Never propose a change without source justification. If no official source supports a proposed wiki change, flag the claim for downgrade or further review instead of writing it as stable guidance.
File boundaries
On confirmation only, this skill may touch:
skills/vitaecontext-<module>/wiki/knowledge.mdskills/vitaecontext-<module>/wiki/index.mdwhen source changes require a different conditional load mapskills/vitaecontext-<module>/SKILL.mdwhen source changes require different routing, load, or high-level operating rulesskills/vitaecontext-<module>/references/*.mdhub/<module>/sources.mdhub/<module>/*.mdllms-full.txt
This skill must never touch:
llms.txtREADME.md- Provider adapter files under
providers/ - Files outside the confirmed list above
Every downstream edit must be source-backed and module-scoped. Do not change hub playbooks, runtime references, module SKILL.md, or wiki/index.md only because the wording could be cleaner. Change them only when official evidence invalidates, narrows, expands, or clarifies the methodology that agents or humans should apply.
If a source change implies that a forbidden file should change, do not edit that file. Flag it in a follow-up section with the exact file, affected section when known, reason, and source URL. This applies to project-level README content, CHANGELOG entries, provider wrappers, install behavior, and files outside the target module.
Mode 1: Single module refresh
Use this mode when the maintainer asks:
Use vitaecontext-wiki-maintenance to refresh the <module> module
Workflow:
- Read
hub/<module>/sources.mdto identify official sources for the surface. - Read
skills/vitaecontext-<module>/wiki/knowledge.mdto understand current claims, confidence labels,last_reviewed, andreview_by. - Search for newer or missing official sources for the same surface. Use source discovery queries that target official domains, specs, help centers, engineering blogs, or maintai