Skip to content

Vinix24/vnx-orchestration / skills/vnx-manager

vnx-manager

Verified

VNX orchestration infrastructure guardian - maintains dispatcher, smart tap, receipt processor, intelligence systems, and documentation.

FileKindSize
@vnx-manager.mdmarkdown9.2 KB
SKILL.mdskill md3.1 KB
references/_MAPPING.mdmarkdown246 B
template.mdmarkdown1.7 KB

template.md

View on GitHub
# VNX Manager Report Template

## Output Location
Write your report to: `$VNX_DATA_DIR/unified_reports/`

## Filename Format
`{timestamp}-{track}-vnx-{title}.md`

Example: `20260202-143000-C-vnx-intelligence-upgrade.md`

## Report Structure

### Summary
Brief overview of VNX system work completed (2-3 sentences)

### Tags (Required)
- [tag1, tag2, tag3]  # Use specific, compound tags (e.g., dispatch-routing, receipt-processing, quality-gate). Avoid general-only tags.

### Implementation
- Components modified (dispatcher, smart tap, receipt processor, intelligence)
- Configuration changes
- Script updates

### System Impact
- Token efficiency change
- Reliability improvements
- Process flow changes
- Observability additions

### Testing
- Scripts tested and validation results
- CI test results (doctor + pytest suites)
- Integration verification

### Evidence
- Command output showing changes work
- Before/after metrics
- CI test pass confirmation

### Documentation Updates
- Architecture docs updated
- Operations docs updated
- Public release docs updated when applicable

### Open Items
<!-- List any unfinished work, blockers, or issues discovered -->
<!-- Format: - [ ] [severity] Title (optional details) -->
<!-- Severities: [blocker], [warn], [info] -->
<!-- Leave empty if all work completed -->

### Recommendations
- Follow-up work needed
- System improvements identified
- Technical debt items

### Intelligence Feedback
<!-- If your dispatch included [INTELLIGENCE_DATA] with offered_pattern_hashes, report which patterns you actually used: -->
used_pattern_hashes: []

## Quality Standards
- All CI tests pass (9/9)
- No hardcoded paths
- Documentation updated
- Changes tested end-to-end
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall