builder-data_skill

This skill queries Talent Protocol to source builder reputation, identity verification, credentials, and GitHub enrichment for verified insights.
  • Python

2.5k

GitHub Stars

2

Bundled Files

3 weeks ago

Catalog Refreshed

2 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstart where the catalogue uses aiagentskills.

npx veilstart add skill openclaw/skills --skill builder-data

  • _meta.json285 B
  • SKILL.md4.7 KB

Overview

This skill queries builder reputation and identity data from the Talent Protocol API to find and verify developers. It returns builder ranks by default, resolves social and wallet identities, and can enrich profiles with GitHub project data. Use it to locate verified builders by location, skills, or linked accounts.

How this skill works

The skill calls Talent Protocol endpoints to search profiles, fetch connected accounts, socials, credentials, and rank data. It prefers ranks (rank_position) unless scores are explicitly requested, and supports identity lookups by Twitter, GitHub, Farcaster, ENS, or wallet. For location-based searches it issues a POST with a customQuery regex; for GitHub enrichment it resolves the username from /accounts and then queries the GitHub API.

When to use it

  • Find ranked builders in a given city or country and sort by Builder Score
  • Verify that a wallet, Twitter, or GitHub handle belongs to a real human
  • Resolve a profile’s linked accounts (GitHub, Twitter, Farcaster, wallet)
  • Fetch credentials like earnings, hackathons, contributions, and contracts
  • Enrich a builder profile with top or recent GitHub repositories and activity

Best practices

  • Always use ranks by default; request raw scores only when needed
  • Use the customQuery regex for location filtering instead of standardized_location
  • Include human_checkmark=true only when you need strict human verification (reduces results)
  • Page results with per_page up to 250 and handle pagination
  • Provide a GITHUB_TOKEN for GitHub enrichment to avoid low rate limits

Example use cases

  • Search for verified developers in Argentina and return top 50 by rank
  • Map a Twitter handle to a wallet and confirm human verification before onboarding
  • Collect a builder’s credentials and earnings for due diligence
  • Resolve a GitHub username from Talent accounts and fetch top 5 repos
  • List designers or developers with specific tags and country-based regex filtering

FAQ

Ranks are returned by default (builder_score.rank_position). Request scores explicitly to receive builder_score.points.

How do I filter by country or city?

Use a POST search/advanced/profiles with a customQuery regexp on standardized_location; the simple standardized_location param is unreliable.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational