Architecture of Neko’s Social Interaction Layer
plugin-twitter
package with its enhanced Actions V2 architecture, this agent leverages modular actions, robust error handling, sophisticated LLM integration, and efficient memory management to perform its functions.
hyperliquidSearchAction
(searching keywords) and hyperliquidUsersAction
(monitoring ~27 key influencers) to fetch relevant tweets via the Twitter API. Can also leverage data fetched by other specialized actions (e.g., dune_apiAction
, hypurrscanAction
) via memory.autoAction
): Can intelligently merge context from various data sources (e.g., Twitter sentiment, Dune metrics, Hypurrscan activity) retrieved from memory to create a comprehensive analysis.templates.ts
) to structure prompts, incorporating the LLM analysis, data placeholders, agent personality/voice guidelines, and platform constraints. The LLM then generates the final tweet text.TWITTER_DRY_RUN
mode is enabled.@neko_hl gneko
on X triggers a tweet linking to the neko.fun application).hyperliquidSearchAction
, hyperliquidUsersAction
) for tweet content and engagement data.dune_apiAction
for on-chain metrics (TVL, volume, etc.).hypurrscanAction
for detailed transaction data and blockchain metrics.autoAction
to retrieve and merge context from different data-fetching actions.plugin-twitter
& Actions V2: Provides modular, robust Twitter interaction capabilities.templates.ts
): Ensures consistent voice, formatting, and data integration in generated content.AutoClient
(packages/client-auto
): Manages scheduled execution of actions (like autoAction
) for automated posting..env
, character JSON files, and runtime secrets (including TWITTER_DRY_RUN
control).