Felo Search on dsh

DeepSeek Harness

Give the session a way to check the world outside the repository

A dsh session can read your files all day and still not know what the vendor changed this week. Felo Search returns dated answers with sources, so the agent can act on what shipped instead of what the lockfile remembers.

Built for dshOne folderNeeds a Felo key

Get an API key See the platform guide

Felo Search on dsh

01Bundle: felo-skills/felo-search
02Credential: FELO_API_KEY
03Comes back as: Claim, source, date
04Root: .dsh/skills/

Mount itcp -r felo-skills/felo-search .dsh/skills/

This skill runs on

DeepSeek Harness

Open-source agent harness (developer preview)

Read the DeepSeek Harness guide

dsh reads skills straight out of folders you point it at, so a Felo bundle is one copy away from being callable in a session — and one delete away from being gone.

Loads from: ~/project/.dsh/skills/ · ~/.agents/skills/
Install is: A folder copy, no build step
Worth knowing: Only direct children of a root are read

What you get back

Every line carries its own sourcing

The point of adding search to a harness is not more text. It is that each claim arrives with the page it came from and the date it was published, so you can throw away the parts you do not trust.

ClaimSourcePublished

The v3 SDK renamed the streaming clientdocs.vendor.com/migrate/v36 days ago

Retry defaults changed from 3 to 5github.com/vendor/sdk/releases6 days ago

The old endpoint still works until Junestatus.vendor.com/deprecations2 weeks ago

Regional latency improved in eu-westvendor.com/blog/edge-rollout9 days ago

Ask for the source list as a requirement, not a courtesy: "cite a source and a date for every item, and mark anything you could not verify."

In practice

Two questions worth asking first

Both of these fail on a repo-only agent, and both come back with sources once the bundle is mounted.

Type thisSearch for the breaking changes in the SDK we just upgraded, and list only the ones that touch this module.What comes back

A short list, each line pointing at a changelog entry or docs page, with the ones that do not affect this module left out.

Type this

Our integration test started failing after the upgrade. Search for reports of the same failure and tell me whether it is our code or the library.

What comes back

A comparison of what other people are hitting against what your stack trace shows, with links so you can judge it yourself.

Add it on dsh

Copy one folder into a root dsh already watches

No package manager, no build step. dsh scans the direct children of its discovery roots, so the whole install is one copy — and the whole rollback is one delete.

~/project/.dsh/skills/Project

Loads for this repository only. The right place to read a bundle before you trust it with the whole machine.

~/.agents/skills/User

Loads in every project, and is the same folder other harnesses on this machine look at.

Mount the bundle

mkdir -p .dsh/skills
cp -r felo-skills/felo-search .dsh/skills/

Prove it loadedList the skills you can call from this project.

Check it worked

Three signs the skill is live in the session

A mounted bundle can still be invisible if the root is wrong or the folder is nested.

The catalog lists it

Ask the session which skills it can call. felo-search should appear by name, not as an unknown tool.

It refuses to guess

Ask something recent and check whether the answer carries dates. An answer with no dates means you are reading a model's memory, not the skill.

It fails loudly without a key

Unset FELO_API_KEY in a scratch shell and run one query. A clear credential error means the skill is wired up; a plausible answer with no key means something is wrong.

Pairs well with

Two more bundles that fit the same research loop

Search answers what is true right now. These two close the rest of the loop.

Felo Web FetchWhen search points at a page you need in full, this turns it into structured data the session can work with.Open the skill page →Felo LiveDocWhen the answer should come from your own documents rather than the open web, this is the other half of the pair.Open the skill page →

FAQ

What dsh users ask about Felo Search

Does this replace the harness's built-in web tool?

No. Built-in browsing usually returns page text, and the session has to decide what matters. This returns an answer with the sources already attached, which is what you want when the result feeds a decision rather than a summary.

Will it run on every turn and slow the session down?

Only when the session decides the task needs current information. Nothing is fetched in the background, so a refactor that never asks about the outside world costs nothing.

Where does the API key live?

In the Felo CLI config, outside the repository. The bundle reads it from there, so you never commit a key and the same key works for every Felo skill you mount.

Can I keep it project-scoped?

Yes, and that is the recommended start. Mount into .dsh/skills/ while you evaluate it, then move the folder to ~/.agents/skills/ when you want it everywhere.

Every Felo skill for DeepSeek Harness

Five skills written for DeepSeek Harness. They follow the same pattern on this platform, so you can combine them in one session without re-explaining your setup.

Felo SearchLive web research with sources you can cite

Felo SlidesGenerate a deck from a single prompt

Felo YouTube SubtitlingTranscripts from talks, demos, and reviews

Felo X SearchTrack posts and replies on X

Felo SuperAgentLong-running workflows that keep their memory

Beyond ready-made skills

One API key. A full agent toolkit.

Start with a skill, then compose the exact models, live data, knowledge, and output tools your dsh workflow needs — the same key every Felo skill already uses.