upgrade-link
Skill8 starsChanged 54 days agoApache-2.0View on GitHub
Provides comprehensive guidance for upgrade link management including upgrade link creation, configuration, and upgrade link best practices. Use when the user asks about upgrade links, needs to create upgrade links, configure upgrade processes, or manage upgrade links.
In this repository6 other files it gives its agents.
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- electron-eggSkill
- electronSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill whenever the user wants to:
- Distinctive: line 9
Use UpgradeLink tool for system upgrades
- Distinctive: line 15
Use UpgradeLink APIs or integrations
- Distinctive: line 16
Follow UpgradeLink best practices
- Distinctive: line 42
All examples follow UpgradeLink official documentation
- Distinctive: line 44
Always check the example file for best practices and common patterns
- Distinctive: line 63
Follow the instructions, syntax, and best practices in that file
- Very specific: line 79
All API files include links to relevant example files in the examples/ directory
- Distinctive: line 83
Follow official documentation: Always refer to official UpgradeLink documentation
- Distinctive: line 84
Test upgrades: Test upgrades in development environment first
- Distinctive: line 85
Backup data: Always backup data before performing upgrades
- Distinctive: line 86
Version compatibility: Check version compatibility requirements
- Distinctive: line 89
Documentation: Document upgrade procedures
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
When to use this skill
Use this skill whenever the user wants to:
- Use UpgradeLink tool for system upgrades
- Understand UpgradeLink features and capabilities
- Perform version migrations
- Configure UpgradeLink settings
- Troubleshoot UpgradeLink issues
- Implement upgrade workflows
- Use UpgradeLink APIs or integrations
- Follow UpgradeLink best practices
How to use this skill
This skill is organized to match the UpgradeLink official documentation structure (https://www.toolsetlink.com/upgrade/what-is-upgrade.html). When working with UpgradeLink:
- Identify the topic from the user's request:
- Getting started/快速开始 →
examples/getting-started/introduction.mdorexamples/getting-started/basic-usage.md - Features/功能特性 →
examples/features/directory - Advanced usage/高级用法 →
examples/advanced/directory
- Getting started/快速开始 →
Load the appropriate example file from the
examples/directory:Getting Started (快速开始) -
examples/getting-started/:examples/getting-started/introduction.md- What is UpgradeLinkexamples/getting-started/basic-usage.md- Basic usage examples
Features (功能特性) -
examples/features/:examples/features/- Feature-specific examples
Advanced (高级) -
examples/advanced/:examples/advanced/- Advanced usage examples
Follow the specific instructions in that example file for syntax, structure, and best practices
Important Notes:
- All examples follow UpgradeLink official documentation
- Each example file includes key concepts, code examples, and key points
- Always check the example file for best practices and common patterns
- Reference API documentation in the
api/directory when needed:api/- API reference documentation
- Use templates from the
templates/directory:templates/- Usage templates
Doc mapping (one-to-one with official documentation)
Examples and Templates
This skill includes detailed examples organized to match the official documentation structure. All examples are in the examples/ directory (see mapping above).
To use examples:
- Identify the topic from the user's request
- Load the appropriate example file from the mapping above
- Follow the instructions, syntax, and best practices in that file
- Adapt the code examples to your specific use case
To use templates:
- Reference templates in
templates/directory for common scaffolding - Adapt templates to your specific needs and coding style
API Reference
Detailed API documentation is available in the api/ directory, organized to match the official UpgradeLink API documentation structure.
To use API reference:
- Identify the API you need help with
- Load the corresponding API file from the
api/directory - Find the API signature, parameters, return type, and examples
- Reference the linked example files for detailed usage patterns
- All API files include links to relevant example files in the
examples/directory
Best Practices
- Follow official documentation: Always refer to official UpgradeLink documentation
- Test upgrades: Test upgrades in development environment first
- Backup data: Always backup data before performing upgrades
- Version compatibility: Check version compatibility requirements
- Error handling: Implement proper error handling
- Logging: Enable logging for troubleshooting
- Documentation: Document upgrade procedures
- Rollback plan: Have a rollback plan ready
Resources
- Official Website: https://www.toolsetlink.com/
- Documentation: https://www.toolsetlink.com/upgrade/what-is-upgrade.html
Keywords
UpgradeLink, upgrade, migration, version, toolsetlink, 升级, 迁移, 版本
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

