api-version

Retrieve Weaver application version, database schema version, and deployed commit hash.

30|6|Updated Mar 5, 2019
One-click install
npx skills add https://github.com/crim-ca/weaver --skill api-version-crim-ca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-version
Source: https://github.com/crim-ca/weaver/tree/main/.agents/skills/api-version
Command: npx skills add https://github.com/crim-ca/weaver --skill api-version-crim-ca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a straightforward way to retrieve detailed version information for the Weaver instance, helping with compatibility checks, troubleshooting, and system configuration verification.

Core Features & Use Cases

  • Version Information Retrieval: Get Weaver version, database schema version, and deployed commit hash.
  • Compatibility Verification: Ensure the Weaver instance is up-to-date with the required versions for compatibility.
  • Troubleshooting: Use the version information to identify and resolve issues.
  • System Configuration: Verify system configuration against expected settings.
  • Use Case: When encountering unexpected behavior or when deploying Weaver, use this Skill to check the version details to ensure compatibility with the current setup.

Quick Start

Use the 'api-version' skill to get the version information for your Weaver instance.

Frequently Asked Questions about api-version

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check Weaver version information for compatibility troubleshooting?

To check Weaver version information for compatibility troubleshooting, retrieve the application version, database schema version, and deployed commit hash to verify your system configuration meets expected requirements.

What version details do I need to verify Weaver system configuration?

Verifying Weaver system configuration requires the application version, database schema version, and deployed commit hash, which together ensure your instance matches expected compatibility settings and aids troubleshooting.

Why does my Weaver instance show unexpected behavior after deployment?

Unexpected Weaver behavior after deployment often stems from version mismatches; retrieving the application version, database schema version, and commit hash helps identify compatibility issues causing the problem.

Can I retrieve the database schema version to troubleshoot Weaver compatibility issues?

Yes, you can retrieve the database schema version alongside the Weaver application version and deployed commit hash to troubleshoot compatibility issues and verify system configuration against expected settings.

Does retrieving version information help with Weaver system configuration verification?

Retrieving version information helps with Weaver system configuration verification by providing the application version, database schema version, and commit hash needed to confirm compatibility and resolve issues.