Skip to content

sandbaseai/sandbase-skills / research/github-profile-research

github-profile-research

Verified

Research GitHub user profiles including repositories, contributions, languages, stars, and activity patterns. Useful for developer talent sourcing, open-source community research, and technical due diligence on engineering teams.

GitHub Profile Research

Research GitHub user profiles including repositories, contributions, languages, stars, and activity patterns. Useful for developer talent sourcing, open-source community research, and technical due diligence on engineering teams. Read the API map before selecting a capability.

Call SandBase capabilities

Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with sandbase_discover(q: "<provider and capability>"); use its returned name in sandbase_inspect(name: "<returned name>"). Read inputSchema, pricing, and execute_as, then call sandbase_run using execute_as.arguments.name and schema-defined arguments. If a run_id is returned, poll sandbase_run_get(run_id: "<returned run_id>") within the task budget until completed or failed; report pending or failed runs without resubmitting them automatically.

Capability identifiers

  • strale_github_user_profile

Workflow

  1. Understand the user's research question, target, and context.
  2. Resolve each selected capability with sandbase_discover, then inspect the returned name with sandbase_inspect to confirm the schema and pricing.
  3. Follow execute_as with sandbase_run; collect async results with sandbase_run_get as described above.
  4. Synthesize findings into a clear, evidence-backed answer.
  5. Cite sources, note evidence gaps, and separate observations from interpretations.

Guidelines

  • Always call sandbase_inspect before using any capability.
  • Cite sources and preserve attribution (URLs, usernames, dates, metrics).
  • Separate factual observations from analysis and recommendations.
  • If data is unavailable, note the gap and continue with available evidence.
  • Read-only research only. Never take actions on platforms.
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 114kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 114kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 114kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 114kUpdated Claude CodeCodexVerifiedInstall