contracts

Redirects deprecated skill-directory usage to the canonical SKILL.md entry point.

7|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/Zodomo/DrandVerifier --skill contracts-zodomo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contracts
Source: https://github.com/Zodomo/DrandVerifier/tree/main/.opencode/skills/ethskills/contracts
Command: npx skills add https://github.com/Zodomo/DrandVerifier --skill contracts-zodomo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the confusion caused by outdated or deprecated skill paths by redirecting you to the current Skill entry point.

Core Features & Use Cases

  • Deprecation handling: Clearly marks the skill as deprecated to prevent new usage of an outdated directory.
  • Accurate discovery: Directs users to the correct, canonical SKILL.md URL for the replacement skill.
  • Practical use: Helps maintainers and users quickly locate the updated Skill definition when integrating or searching in automated systems.

Quick Start

Open the updated Skill at https://ethskills.com/addresses/SKILL.md to retrieve the current contracts skill definition.

Frequently Asked Questions about contracts

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

FAQPage Schema
How do I resolve a deprecated skill directory path during repository integration?

To resolve a deprecated skill directory path, redirect to the canonical SKILL.md entry point to load operational metadata from the updated URL. This preserves consistent name and description discovery behavior during repository integration workflows.

What happens when I try to load metadata from a moved skill location?

When loading metadata from a moved skill location, the deprecated directory is bypassed by directing you to the current SKILL.md URL. This prevents new usage of outdated paths while maintaining accurate skill discovery.

Why does my repository integration fail to find the contracts skill metadata?

Repository integration fails to find contracts skill metadata because the original path has moved and is marked as deprecated. You must retrieve the current skill definition from the updated canonical SKILL.md URL to resolve the discovery failure.

How do I update my automated systems to use the canonical SKILL.md entry point?

To update automated systems, replace outdated directory references with the canonical SKILL.md URL to retrieve the current skill definition. This ensures maintenance and search workflows load accurate metadata from the updated location.

When should I use a deprecated skill redirect instead of deleting the old directory?

Use a deprecated skill redirect instead of deleting the old directory when you need to preserve consistent name and description discovery behavior for existing integrations. This clearly marks the directory as deprecated while directing users to the updated replacement.