builder-data

What This Skill Does

The builder-data skill enables your OpenClaw AI agent to interface directly with the Talent Protocol API, acting as a powerful search engine for the professional web3 builder ecosystem. It allows the agent to verify developer identities, cross-reference social profiles (Twitter, Farcaster, GitHub), and retrieve granular reputation data. By leveraging this skill, you can move beyond simple searches to discover validated contributors based on specific hackathon history, technical skills, and verified rank positions, making it an essential tool for community managers, recruiters, and ecosystem researchers.

Installation

To integrate this tool into your agent, use the OpenClaw installation command: clawhub install openclaw/skills/skills/juampihernandez/talent-powers

Ensure you have your TALENT_API_KEY ready. You can obtain this from the Talent Protocol settings page. If you plan on performing high-volume queries related to GitHub, it is highly recommended to also set your GITHUB_TOKEN to prevent rate-limit throttling.

Use Cases

• Talent Acquisition: Identify top-ranked developers in specific geographic regions or those who have successfully participated in major hackathons.
• Identity Verification: Perform due diligence on web3 entities by mapping wallet addresses to their respective Twitter or Farcaster profiles.
• Community Building: Analyze the developer distribution within a project by filtering users based on specific skill tags or reputation scores.
• Contributor Enrichment: Fetch detailed credential information to evaluate a builder's past work, earnings, and shipping history.

Example Prompts

1. "Find me the top 10 ranked developers who have a GitHub account linked and are located in Berlin."
2. "Verify if the wallet address 0x123... is a human-verified builder on Talent Protocol and tell me their current builder rank."
3. "Show me the recent contributions and skill tags for the Twitter user @dev_handle."

Tips & Limitations

• Ranking vs. Scoring: By default, the skill returns rank positions. Only request 'scores' when you explicitly need the raw numerical values.
• Location Filtering: Do not attempt to use standardized_location. Always rely on customQuery with regex for geographic searches to ensure accuracy.
• Rate Limiting: If you are performing large-scale batch analysis, ensure your GITHUB_TOKEN is configured to boost your limits from 60 requests per hour to 5,000.
• Human Verification: Use human_checkmark sparingly; while it increases result quality, it significantly restricts the volume of potential profiles returned, potentially hiding high-quality builders who haven't completed the specific verification step.