dming/package-version-first
.cursor/skills/package-version-first/SKILL.md
Always bump extension version in package.json before packaging VSIX. Use when user asks to package, build release artifacts, generate VSIX, publish, or prepare an installable extension package.
$ install --global
skillsauthnpx skillsauth add dming/vscode-blueprint package-version-firstInstall 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 17, 2026, 10:22 AM4.6s1 file scanned
SKILL.md
- name:
- package-version-first
- description:
- Always bump extension version in package.json before packaging VSIX. Use when user asks to package, build release artifacts, generate VSIX, publish, or prepare an installable extension package.
Package Version First
Rule
For this project, every packaging workflow must bump package.json version first, then run npm run package.
Never package first and bump later.
Trigger Scenarios
Apply this skill when user asks to:
- package extension
- build a VSIX
- generate an installable package
- prepare release artifact
- publish extension build
Required Workflow
- Read current
package.jsonversion. - Decide target version:
- If user provided exact version, use it.
- If user did not provide version, default to patch +1 (e.g.
2.0.1-4->2.0.1-5) and execute directly.
- Update
package.jsonversionfield. - Run
npm run package. - Report final VSIX path and version.
Output Format
When done, always include:
- New version number
- Absolute VSIX path
- Packaging result (success/failure)
Related Skills
dming/blueprint-json-contracts
development
VerifiedTrustedCommunity
Before changing blueprint.config.json or *.bp.json shapes (or parsers/adapters), read the shared JSON contract TypeScript files. Use when editing config, editor documents, serialization, migration, or runtime asset bridges.
1SKILL.mdUpdated Apr 17, 2026
dming/blueprint-dev-resume
development
VerifiedTrustedCommunity
Resume blueprint editor development quickly with a fixed startup checklist, regression checks, and end-of-session handoff updates. Use when user says continue development, resume work, or asks to keep iteration momentum.
1SKILL.mdUpdated Apr 17, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,764SKILL.mdUpdated Apr 10, 2026