Discover Blockchain skills, compare source repositories and read the instructions for each workflow.
Diagnose and fix common snforge test errors including Sierra compilation failures, cost computation cycles, and version mismatches; use when tests fail with cryptic errors even though `scarb build` succeeds.
Explain how to write and run Cairo tests, including `#[test]`, assert macros, `#[should_panic]`, `#[ignore]`, and `#[available_gas]`; use when a request involves writing or running unit tests in Cairo.
Run test and lint validation gate. Use after implementation to verify code quality.
Collect and research materials for X (Twitter) content creation using multi-round web search strategy. Use when user wants to gather trending topics, research subjects for X posts, or mentions "collect material...
Score and filter topics for X content creation using weighted criteria. Use when user wants to evaluate collected materials, filter topics by score, or mentions "filter topics", "score materials", "x-filter", "...
Create viral X (Twitter) posts including short tweets, threads, and replies. Use when user wants to write X content, create posts, or mentions "create tweet", "write thread", "x-create", "写推文", "创作推文". S...
Explore ideas through conversation. HOUSTON asks questions, has opinions, and suggests background agents when investigation would help.
Cosmos SDK module development patterns and conventions for Celestia
Explain Starknet L1 and L2 messaging, l1_handler functions, and message syscalls; use when a request involves cross layer messaging in Cairo.
Explain Starknet storage cost optimization, packing values, and bitwise operations; use when a request involves reducing storage slots or implementing packed storage in Cairo.
Explain Cairo hashing with Poseidon and Pedersen, Hash/HashState traits, and hashing structs/arrays; use when a request involves computing hashes or deriving Hash in Cairo.
Explain Starknet-specific types like ContractAddress, StorageAddress, ClassHash, EthAddress, BlockInfo, and TxInfo; use when a request involves these core Starknet types in Cairo.
Explain Starknet storage mappings with Map, hashing of keys, and read/write patterns; use when a request involves mapping-like storage in Cairo.
Explain Cairo packages and crates, Scarb project layout, and crate roots; use when a request involves creating projects or understanding package/crate structure in Cairo.
Explain Starknet contract entry points (external, view, constructor, l1 handler) and ABI configuration; use when a request involves defining or exposing contract functions in Cairo.
Explain how to test Starknet contracts with Foundry tools, deploy and call contracts, and use cheatcodes; use when a request involves contract test setup or testing patterns.
Explain the Starknet contract class ABI, entry points, selectors, and dispatcher usage; use when a request involves ABI JSON, entry point metadata, or how calldata is encoded for contracts.
Explain Starknet contract classes vs instances, class hash, contract deployment, and upgrade patterns; use when a request involves declaring/deploying contracts or understanding class hashes in Cairo.
Explain Starknet components, embedding into contracts, and component interfaces; use when a request involves reusable contract logic or component-based design in Cairo.
Summarize Starknet smart contract security recommendations and common Cairo pitfalls; use when a request involves best practices, safety checks, or audit guidance.
Explain Starknet ABI serialization of Cairo types, including arrays, structs, enums, and integers; use when a request involves calldata encoding or Serde behavior.
Explain Starknet contract events, event enums, and emitting events; use when a request involves defining or emitting events in Cairo.
Explain Starknet storage vectors with VecTrait and MutableVecTrait, element addressing, and operations; use when a request involves Vec-based storage in Cairo contracts.
Explain Starknet upgradeability via class hash replacement and proxy patterns; use when a request involves upgrading contract logic or replace_class_syscall.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.