agentleFS
full-stack-skillsfull-stack-skills/electron-skills/skills/upgrade-link/SKILL.md

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.

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
  1. Distinctive:

    Use this skill whenever the user wants to:

    line 8
  2. Distinctive:

    Use UpgradeLink tool for system upgrades

    line 9
  3. Distinctive:

    Use UpgradeLink APIs or integrations

    line 15
  4. Distinctive:

    Follow UpgradeLink best practices

    line 16
  5. Distinctive:

    All examples follow UpgradeLink official documentation

    line 42
  6. Distinctive:

    Always check the example file for best practices and common patterns

    line 44
  7. Distinctive:

    Follow the instructions, syntax, and best practices in that file

    line 63
  8. Very specific:

    All API files include links to relevant example files in the examples/ directory

    line 79
  9. Distinctive:

    Follow official documentation: Always refer to official UpgradeLink documentation

    line 83
  10. Distinctive:

    Test upgrades: Test upgrades in development environment first

    line 84
  11. Distinctive:

    Backup data: Always backup data before performing upgrades

    line 85
  12. Distinctive:

    Version compatibility: Check version compatibility requirements

    line 86
  13. Distinctive:

    Documentation: Document upgrade procedures

    line 89

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Identify the topic from the user's request:
    • Getting started/快速开始 → examples/getting-started/introduction.md or examples/getting-started/basic-usage.md
    • Features/功能特性 → examples/features/ directory
    • Advanced usage/高级用法 → examples/advanced/ directory
  2. Load the appropriate example file from the examples/ directory:

    Getting Started (快速开始) - examples/getting-started/:

    • examples/getting-started/introduction.md - What is UpgradeLink
    • examples/getting-started/basic-usage.md - Basic usage examples

    Features (功能特性) - examples/features/:

    • examples/features/ - Feature-specific examples

    Advanced (高级) - examples/advanced/:

    • examples/advanced/ - Advanced usage examples
  3. 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
  4. Reference API documentation in the api/ directory when needed:
    • api/ - API reference documentation
  5. 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:

  1. Identify the API you need help with
  2. Load the corresponding API file from the api/ directory
  3. Find the API signature, parameters, return type, and examples
  4. Reference the linked example files for detailed usage patterns
  5. All API files include links to relevant example files in the examples/ directory

Best Practices

  1. Follow official documentation: Always refer to official UpgradeLink documentation
  2. Test upgrades: Test upgrades in development environment first
  3. Backup data: Always backup data before performing upgrades
  4. Version compatibility: Check version compatibility requirements
  5. Error handling: Implement proper error handling
  6. Logging: Enable logging for troubleshooting
  7. Documentation: Document upgrade procedures
  8. Rollback plan: Have a rollback plan ready

Resources

Keywords

UpgradeLink, upgrade, migration, version, toolsetlink, 升级, 迁移, 版本

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.