agentleFS
LeostrukaLeostruka/devin-bundle/skills/agent-reach/SKILL.md

agent-reach

Skill0 starsChanged 3 months agoMITView on GitHub

Use when researching trends or public sources across credential-free channels (GitHub, YouTube, Bilibili, V2EX, generic web). Routes to extensions/agent-reach/wrapper.py, a whitelist passthrough to the agent-reach CLI. Credential/cookie channels are out of scope.

44 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use humanizer-zh, obsidian-bases and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • huangservaSkill

    humanizer-zh

    Also in 3 projects that use this

  • wangzhuofengSkill

    obsidian-bases

    Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.

    Also in 3 projects that use this

  • wangzhuofengSkill

    obsidian-markdown

    Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

    Also in 3 projects that use this

  • OpenAISkill

    brainstorming

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

    Also in 7 projects that use this

  • OpenAISkill

    using-git-worktrees

    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

    Also in 4 projects that use this

  • PostHogSkill

    karpathy-guidelines

    Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria. Based on https://github.com/multica-ai/andrej-karpathy-skills.

    Also in 3 projects that use this

  • +2 more from openai

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All output is JSON (status, command, stdout, stderr, duration_s).

    line 35
  2. Distinctive:

    No flags forwarded to the CLI.

    line 53

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agent Reach

Trend and source research via extensions/agent-reach/wrapper.py -- thin passthrough to agent-reach on PATH (or uv tool run agent-reach).

Scope: credential-free only

Whitelisted channels: github, youtube, bilibili, v2ex, web, doctor. These need no account, cookie jar, or API key.

Rejected by design (bundle credential policy -- no credentialed scraping at the bundle boundary): twitter, x, reddit, instagram, xiaohongshu, boss. Requests for these return status: rejected with the reason; do not work around the block.

Commands

W=extensions/agent-reach/wrapper.py

python $W doctor                       # probe agent-reach / uv invoker
python $W github <query args>          # repos, trends, issues
python $W youtube <query args>         # videos, transcripts metadata
python $W bilibili <query args>
python $W v2ex <query args>
python $W web <url|query args>         # generic public web fetch

All output is JSON (status, command, stdout, stderr, duration_s); missing toolchain reports status: missing.

Workflow

  1. doctor once per session; confirm invoker.
  2. Query whitelisted channels; positional args only, no flag passthrough.
  3. Cross-check findings across two channels before citing.

Composition

  • research skill: synthesize wrapper output into cited findings.
  • social-midia: when the task is publishing/monitoring rather than source gathering; keep credentialed actions there, not here.

Boundaries

  • Credential-free channels only; rejection is policy, not a bug.
  • No flags forwarded to the CLI; positional args only.
  • Output bounded at 1 MiB per stream; 120s timeout.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.