new-config

Generate a diffyscan verification config for a deployed smart contract.

142|19|Updated Apr 22, 2023
One-click install
npx skills add https://github.com/lidofinance/diffyscan --skill new-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-config
Source: https://github.com/lidofinance/diffyscan/tree/main/.claude/skills/new-config
Command: npx skills add https://github.com/lidofinance/diffyscan --skill new-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a ready-to-use diffyscan verification config for a deployed smart contract, reducing manual setup time and errors.

Core Features & Use Cases

  • Config generation: Produce a complete diffyscan config with required fields (chain, network, contract addresses, GitHub repo, commit, and relative root).
  • Input guidance: Clarify inputs and dependencies to ensure a valid, upgrade-friendly config.
  • Use Case: When you deploy a new contract, generate the config to immediately verify it with diffyscan.

Quick Start

Provide the required details (chain, contract address, GitHub repo URL, commit hash, and relative root) to generate the new config file.

Frequently Asked Questions about new-config

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

FAQPage Schema
How do I generate a diffyscan verification config for a deployed smart contract?

To generate a diffyscan verification config, provide the target chain, network, contract address, GitHub repo URL, commit hash, and relative root. The tool outputs a validated YAML file with required fields and optional dependency sections for immediate smart contract verification.

What inputs do I need to create a diffyscan config for onboarding new contract deployments?

Creating a diffyscan config requires the chain, network, contract addresses, GitHub repo URL, commit hash, and relative repo root. Supplying these inputs ensures the generated config enforces schema validation and includes required YAML frontmatter for deployment verification.

When do I need to use a diffyscan config file for smart contract verification?

You need a diffyscan config file when onboarding new deployments to verify deployed smart contracts against source code. It reduces manual setup time and errors by automatically structuring your GitHub repository details and contract addresses into a validated schema.

Does the diffyscan config schema support optional fields for dependencies and integration details?

Yes, the diffyscan config schema validates required fields like chain and contract addresses while allowing optional sections for dependencies and integration details. This ensures the config remains upgrade-friendly and accommodates complex smart contract deployment setups.

Can I automate diffyscan config generation for multiple contract addresses on the same network?

Generating a diffyscan config accepts contract address inputs to build a verification file for deployed smart contracts. By providing the specific network, GitHub repository URL, and relative root, the schema validates multiple addresses under a single deployment configuration.