github-dataforseo skillA
github-dataforseo is agent-read markdown (skill) from avalonreset/legends-github: Research repository search demand and SERP intent through legends-dataforseo-kit, without MCP..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Repository search research Use the portable `legends_github.py research` command. Install the toolkit's `requirements-dataforseo.txt` before live acquisition. Read `docs/SEO-RESEARCH.md` from the toolkit root. No agent-specific host configuration is required. 1. Inspect the product and audience; propose bounded relevant keyword seeds. 2. Declare location and language. Run an estimate without `--execute` first. 3. Follow the user's authorization for paid research. Execute with an explicit `--confirm-cost-usd` ceiling. Never expose credentials or retry paid requests blindly. 4. Preserve exports and timestamps. Inspect search intent and product fit before selecting a primary keyword. Missing demand is unknown, not zero. 5. Import the exports with `seo --keyword-data --primary-keyword --serp-data`. 6. Recommend specific copy, topics, examples and comparisons. Report these as hypotheses until traffic or ranking measurements support an outcome. DataForSEO keyword volume describes web search demand, not GitHub internal search demand. This connector implements keyword overview and Google organic SERPs; it does not establish AI citation visibility or competitor revenue.
Read the whole file at its exact version.
How to install
mdr add avalonreset/legends-github/github-dataforseo@git:20260921.1b04d43mdr add avalonreset/legends-github/github-dataforseo@sha256:5eb64afeee4bbf48Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_e2777x3k5oohff4u)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260921.1b04d43 latest | 2026-09-21 | 1b04d43 | 1,335 B | A | view · diff |
| git:20260313.aa9b904 | 2026-03-13 | aa9b904 | 4,717 B | A | view · diff |
| git:20260309.d019325 | 2026-03-09 | d019325 | 4,720 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1335 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
avalonreset/legends-github · 4 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_e2777x3k5oohff4u GET https://markdownregistry.com/api/v1/resolve?ref=avalonreset/legends-github/github-dataforseo GET https://markdownregistry.com/api/v1/blob/5eb64afeee4bbf48a5f28c3bc37727b24000e1b4ff00c9fd434cd576737b3978
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.