Skip to content
Back to skills

Seltz

ASecurity

Use Seltz's official MCP search tool for current, source-backed web research in Codex.

  • 1,531 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentsapisecurity

Works with

  • api
  • mcp

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add hashgraph-online/awesome-codex-plugins --skill seltz --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Seltz?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Seltz
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hashgraph-online-seltz/badge)](https://www.skillsdirectory.com/skills/hashgraph-online-seltz)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: seltz
description: Use Seltz's official MCP search tool for current, source-backed web research in Codex.
license: Apache-2.0
---

# Seltz web research

Use the configured Seltz MCP server when the user needs current web information, recent developments,
source discovery, or a fact check. The server exposes Seltz's documented tools for web search and page
fetching; take their parameters and limits from the live tool definitions, which are documented on the
[Seltz MCP page](https://docs.seltz.ai/integrations/mcp).

## Operating rules

1. Turn the user's request into a concise, specific query. Include a date, jurisdiction, product, or
   domain when it materially narrows the research question.
2. Request only as many results as the task needs. Ask for more only when the first results leave a clear
   evidence gap.
3. Preserve source URLs and publication dates from the tool result. Distinguish Seltz output from your
   own synthesis, and tell the user when a claim is time-sensitive or only supported by one source.
4. Prefer primary, official, or directly attributable sources for legal, financial, medical, security,
   and product claims. Do not treat ranking as proof.
5. Do not send API keys, passwords, payment credentials, private account data, or unnecessary personal
   information in a query.
6. Do not imply that Seltz verified a fact or returned an exhaustive result set unless the live tool
   response explicitly supports that statement. When the contents of a specific page matter, fetch that
   page instead of quoting a search snippet.

## Failure handling

- Authentication or permission failures: ask the user to reconnect Seltz in Codex and sign in again;
  never ask them to paste a key or other credential into the conversation.
- Rate, usage, or balance limits: report the limit, honor any retry timing returned by the server, and do
  not loop.
- Timeouts or unavailable service: retry at most once when the request is safe and idempotent, then offer
  a fallback that does not pretend to have current Seltz data.
- Malformed or incomplete results: say what is missing, preserve any usable source links, and do not
  manufacture fields or citations.

## Safe response pattern

For research answers, state the question and retrieval time, summarize the strongest sources, link them,
and call out uncertainty, conflicting evidence, or missing coverage. For fact checks, separate the verdict
from the evidence and explain what would change the conclusion.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.