mcpField
T
thor

thor

github.com/vechainDevelopment1578 installsUpdated 4w ago
Repository

About thor

thor is a skill for answering questions about the VeChainThor node and its Go codebase. It directs users to topic-specific references for architecture, consensus, APIs, storage, networking, operations, and contribution workflows.

Key features

  1. 01Topic-based reference file selection
  2. 02Coverage of node architecture and operations
  3. 03Consensus and contract documentation
  4. 04API, storage, and networking references
  5. 05Transaction and chain flow guidance

Use cases

  1. 01Understanding a VeChainThor node component
  2. 02Tracing consensus or transaction flows
  3. 03Finding contribution and build guidance

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/vechain/vechain-ai-skills --skill thor

After installing, type/thorin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
api.md
architecture.md
built-in-contracts.md
consensus.md
contributing.md
flow-block-production.md
flow-reward-distribution.md
flow-staking-delegation.md
flow-sync.md
flow-transaction-lifecycle.md
p2p.md
solo.md
storage.md

Details

From the project README

Thor Skill

CRITICAL RULES

  1. Read reference files FIRST. When the user's request involves any topic in the reference table below, read those files before doing anything else. Briefly mention which files you are reading so the user can confirm the skill is active.
  2. Information priority: (a) Reference files in this skill — always the primary source. (b) The thor repo source code at github.com/vechain/thor/v2 for implementation details. (c) Web search — only as a last resort for topics NOT covered in references.
  3. Prefer working directly in the main conversation. Plan mode and subagents do not inherit skill context and may produce stale answers.
  4. After compaction or context loss, re-read this SKILL.md to restore awareness of the reference table.

Scope

Use this Skill for anything related to the VeChainThor node (thor):

  • Architecture and package structure of the Go codebase
  • Consensus: PoA v1/v2, PoS (Galactica), BFT finality
  • Built-in contracts: Authority, Energy, Staker, Params, Prototype, Executor, Extension
  • REST API endpoints and WebSocket subscriptions
  • Storage: LevelDB, SQLite logdb, trie, pruning, node types
  • P2P networking: discovery, block/tx propagation
  • Cross-cutting flows: block production, transaction lifecycle, reward distribution, staking/delegation, chain sync
  • Solo mode for local development
  • Contributing to the thor codebase: build, test, add endpoints, fork config

For application-level VeChain development, see the companion skills:

  • vechain-core — SDK usage, fee delegation, multi-clause transactions, dual-token model
  • vechain-kit — VeChain Kit hooks, components, wallet connection, social login
  • smart-contract-development — Solidity, Hardhat, testing, security
  • stargate — NFT staking, validator delegation, VTHO rewards

Operating procedure

1. Identify the question type
  • PM/architecture question → read architecture.md + relevant flow files
  • Contributor question → read contributing.md + relevant package reference
  • "How does X work?" → read the matching flow file(s)
  • API question → read api.md
  • Node operations → read architecture.md (node types, flags, ports)
2. Read before answering

Load the matching reference files from the table below. Cross-cutting questions may need multiple files.

3. Answer with context
  • Reference specific packages, types, and files from the thor codebase
  • For flows, trace through the packages step-by-step
  • For PM audiences, lead with the high-level summary before diving into implementation
  • For contributors, include package paths and key type names

Reference files

Read the matching files BEFORE doing anything else. See Critical Rules above.

TopicFileRead when user mentions...
Architecturereferences/architecture.mdoverview, packages, node types, ports, flags, fork config, tech stack
Consensusreferences/consensus.mdPoA, PoS, BFT, finality, proposer, validator selection, VRF, Galactica
Built-in contractsreferences/built-in-contracts.mdAuthority, Energy, VTHO, Staker, Params, Prototype, Executor, native contracts
REST APIreferences/api.mdAPI, endpoints, routes, subscriptions, WebSocket, Swagger
Storagereferences/storage.mddatabase, LevelDB, SQLite, logdb, trie, pruning, archive, disk
P2P networkingreferences/p2p.mdpeers, discovery, discv5, propagation, sync protocol, bootstrap
Contributingreferences/contributing.mdbuild, Makefile, tests, lint, add endpoint, fork config, PR, Go conventions
Solo modereferences/solo.mdsolo, local dev, test chain, pre-funded accounts, auto-mine
Flow: block productionreferences/flow-block-production.mdblock packing, scheduler, proposer, how blocks are created
Flow: transaction lifecyclereferences/flow-transaction-lifecycle.mdtx flow, txpool, clause execution, receipts, tx validation
Flow: reward distributionreferences/flow-reward-distribution.mdrewards, VTHO generation, validator rewards, gas rewards, burning
Flow: staking & delegationreferences/flow-staking-delegation.mdstaking, delegation, unstaking, Staker contract, validator lifecycle
Flow: chain syncreferences/flow-sync.mdsync, catch-up, peer download, fork handling, reorg, propagation

Comments

Markdown supported