Skip to content
Skills Library
Science & research · Research

github-gem-seeker

/github-gem-seeker

Research and evaluate github gem seeker with current authoritative sources, provenance, and explicit evidence gaps. Use when the user asks for github gem seeker findings or verification.

Licence
Apache-2.0
Last repository change
26.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.09.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Research and evaluate github gem seeker with current authoritative sources, provenance, and explicit evidence gaps. Use when the user asks for github gem seeker findings or verification.

Original author description

Research and evaluate github gem seeker with current authoritative sources, provenance, and explicit evidence gaps. Use when the user asks for github gem seeker findings or verification.

How it works

  1. Workflow
  2. Quality gates
  3. SandBase boundary
  4. Handoff
Original SKILL.md headings · 40 lines, 394 words
SKILL.md preview
---
name: github-gem-seeker
description: "Research and evaluate github gem seeker with current authoritative sources, provenance, and explicit evidence gaps. Use when the user asks for github gem seeker findings or verification."
---

# GitHub Gem Seeker

Use this Skill to produce a bounded, verifiable GitHub Gem Seeker outcome. Preserve the user's chosen stack, source material, and authorization boundaries.

Read [the SandBase API map](references/sandbase-api-map.md) only when the task genuinely needs an external data source or generative model.

## Workflow

1. Inspect the available files, runtime, versions, inputs, and existing conventions before deciding what to change.
2. Restate the requested outcome, constraints, acceptance checks, and any assumption that could change the result.
3. Produce the smallest complete implementation, analysis, or artifact that satisfies those checks.
4. Verify the real output with appropriate tests, previews, calculations, or source comparison; do not infer success from file creation alone.
5. Return the deliverable, evidence of validation, material assumptions, and unresolved limitations.

## Quality gates

- Translate the request into answerable questions and source-selection criteria before searching.
- Prefer primary or official sources, record publication and retrieval dates, and cross-check material claims.
- Return source-linked findings, disagreements, limitations, and unresolved gaps rather than false certainty.
- Respect site terms and rate limits, keep retrieval bounded, and distinguish observed metadata from qualitative recommendations.

## SandBase boundary

Keep the core GitHub Gem Seeker work local. Use SandBase only for current external evidence, search, scraping, enrichment, or model inference that is not already available through the user's authorized tools.

1. Call `sandbase_discover` with a short capability query.
2. Call `sandbase_inspect` for viable candidates and compare the live schema, coverage, limits, output, execution mode, and price.
3. Prefer a dedicated tool or API the user already has. Send only the minimum necessary data.
4. Before any paid call, show the endpoint, important arguments, current unit price, call count, and total estimate or uncertainty, then obtain confirmation.
5. Use `sandbase_account` before an approved multi-call batch and call `sandbase_run` only with current schema-defined arguments.
6. Poll asynchronous work with `sandbase_run_get` using the same run ID; never resubmit merely because it is pending.
7. Use `sandbase_runs` only to recover status or reconcile observed cost.

If SandBase is unavailable, continue with local work and authorized sources when possible. Do not silently switch providers, fabricate external results, or claim a generation or retrieval succeeded.

## Handoff

Provide the completed artifact or findings, concise reproduction steps, checks actually run, source or asset provenance, SandBase endpoint and run IDs when used, observed cost when available, and any follow-up that still requires user action.
Files in this package (2)
  • SKILL.md 3 KB
  • references/sandbase-api-map.md 1 KB

Versions

The database has no other skills named github-gem-seeker.

Database snapshot: 13.11.2026 · package version 5b580267cbf7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 96docs-seeker
    Use when the user asks to find current technical documentation.
  • 100seeker-connect
    Connect a web, React Native, or Kotlin dapp to the Seeker device's built-in wallet with Seeker Connect. Use when adding wallet connection, sign-in with Solana, message signing, or transaction signing to an Expo or React Native app on a Seeker phone, a Kotlin app on it, or a…
  • 90seo-competitor-analysis
    Research and evaluate seo competitor analysis with current authoritative sources, provenance, and explicit evidence gaps. Use when the user asks for seo competitor analysis findings or verification.
  • 90microsoft-docs
    Research and evaluate microsoft docs with current authoritative sources, provenance, and explicit evidence gaps. Use when the user asks for microsoft docs findings or verification.
  • 90vc:docs-seeker
    Search library/framework documentation via llms.txt (context7.com). Use for API docs, GitHub repository analysis, technical documentation lookup, latest library features.
  • 90vc:docs-seeker
    Search library/framework documentation via llms.txt (context7.com). Use for API docs, GitHub repository analysis, technical documentation lookup, latest library features.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.