agentleFS
Sign inStart free
glideaglidea/supersearch-skills/skills/linuxdo-search/SKILL.md

linuxdo-search

Skill4 starsChanged 3 months agoMITView on GitHub

Search linux.do for Chinese community discussions about emerging AI tools, practical experience, promotions, and firsthand reports. Search only linux.do and return source-post links.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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:

    Use only returned citations as sources.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Linux DO Search

Run:

node scripts/search.mjs "search query"

Use only returned citations as sources. When search_executed is false, state that the upstream search did not run and do not treat model-generated links as reliable citations.

End every response with a ## References section. Keep links next to supported claims and repeat the used links here, deduplicated and comma-separated on one website line:

## References

Linux DO: [result title](https://example.com), [result title](https://example.com)

List only links actually used in the answer. When none exist, write No citable sources. below the heading.

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.

Check your setup, free