als-apg/osprey-migrate
src/osprey/assist/integrations/claude_code/migrate/SKILL.md
Upgrades downstream OSPREY projects to newer versions. Applies API changes (method renames, class renames, import changes) from migration documents. Use when upgrading OSPREY version, migrating from old APIs, or when the user asks to upgrade, migrate, or update their OSPREY project.
$ install --global
skillsauthnpx skillsauth add als-apg/osprey osprey-migrateInstall 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 3, 2026, 4:00 PM4.1s1 file scanned
SKILL.md
- name:
- osprey-migrate
- description:
- >
- allowed-tools:
- Read, Glob, Grep, Bash, Edit
OSPREY Migration Assistant
This skill helps you upgrade your OSPREY-based project to a newer version.
Instructions
Follow the detailed migration workflow in instructions.md.
Data Files
- Migration documents: versions/ - YAML files describing changes for each version
- Schema: schema.yml - Migration document format specification
Quick Reference
- Ensure clean git state
- Detect current OSPREY version
- Load migration YAML for target version
- Show dry-run report of all changes
- Apply changes after user confirmation
- Run validation commands
- Provide summary and next steps
Related Skills
als-apg/sim-scenarios
data-ai
VerifiedTrustedCommunity
List, inspect, and switch the simulated machine scenarios that drive the mock control system and mock archiver. Use when the user asks which scenarios are available, which scenario is active, or wants to switch the simulated machine into a different state (e.g. a fault demo or back to nominal).
62SKILL.mdUpdated Jun 13, 2026
als-apg/osprey-build-interview
development
VerifiedTrustedCommunity
Interactive interview to create a custom OSPREY build profile for a new accelerator, detector, or beamline application. Use when someone says "interview me", "create a build profile", "set up my agent", "configure my detector", "onboard me", or needs to create an OSPREY project tailored to their specific control system. Also handles migration from existing OSPREY projects (including LangGraph-era projects) — trigger on "migrate my project", "I have an existing project", "upgrade from old OSPREY", "upgrade from langgraph", "legacy migration", "bring my project forward", "convert my project", "extract profile from existing project", "reverse-engineer build profile". Also use for /osprey-build-interview feedback to collect post-use feedback. Also trigger when onboarding a new colleague or when anyone needs help figuring out what their OSPREY agent should look like.
59SKILL.mdUpdated May 6, 2026
als-apg/osprey-release
testing
VerifiedTrustedCommunity
Guides a maintainer through cutting an OSPREY release on the GitHub Flow workflow: open a version-bump PR, merge it to main, tag the merge commit, push the tag, verify the automated PyPI publish. Use when someone says "create a release", "bump the version", "cut v2026.X.Y", "publish to PyPI", "tag a release", or asks about the release process. Composes with `osprey-contribute` for the bump PR. Versions follow CalVer (vYYYY.M.P) and the source of truth is `src/osprey/__init__.py` — Hatch derives the pyproject.toml version dynamically.
56SKILL.mdUpdated May 6, 2026
als-apg/osprey-pre-commit
development
VerifiedTrustedCommunity
Validates code before committing using OSPREY's three-tier check scripts. Runs linting, formatting, and tests to catch issues early. Use when ready to commit, before pushing, before opening a PR, or when the user asks to run checks, validate, or verify their changes. For the full contribution journey (branching, commits, push, PR, merge), use `osprey-contribute` instead — this skill is the focused validation step.
56SKILL.mdUpdated May 6, 2026