Pilot Service Agents Language

v1.0.0

Language and NLP services — translation, text-to-speech, dictionaries, word tools, Bible text, linguistic corpora. Use this skill when: 1. Translating text b...

0· 28·0 current·0 all-time
byCalin Teodor@teoslayer

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for teoslayer/pilot-service-agents-language.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Pilot Service Agents Language" (teoslayer/pilot-service-agents-language) from ClawHub.
Skill page: https://clawhub.ai/teoslayer/pilot-service-agents-language
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required binaries: pilotctl
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install pilot-service-agents-language

ClawHub CLI

Package manager switcher

npx clawhub@latest install pilot-service-agents-language
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description match the runtime instructions: the SKILL.md tells the agent to use pilotctl to discover and query language/NLP agents on the Pilot overlay. Requiring pilotctl, the pilot-protocol core skill, and a daemon joined to network 9 is consistent with that purpose.
Instruction Scope
The instructions stay on-purpose (use pilotctl to send /help, /data, /summary and read pilotctl inbox). However, any queries and text you send are transmitted to remote agents on the overlay and upstream URLs returned by those agents (the response shape includes an upstream_url). The /summary path references a Gemini-generated prose string, which implies use of a third-party LLM for summaries. Avoid sending secrets or private data because the skill forwards user-provided query text off-host.
Install Mechanism
Instruction-only skill with no install spec or code files — minimal disk footprint and no automatic downloads. This is the lowest-risk install model.
Credentials
The skill declares no environment variables or credentials (proportionate). It does, however, require a running pilot-protocol daemon and network membership (network 9) which gives the agent network-level connectivity to remote peers; that network access is necessary for the skill but increases the blast radius for any data you send.
Persistence & Privilege
always is false and the skill does not request elevated system presence or modifications to other skills. Autonomous invocation is allowed by platform default (not a red flag by itself).
Assessment
This skill appears to do what it says: it uses pilotctl to query language/NLP agents on the Pilot overlay and returns structured responses. Before installing, verify you trust the pilotctl binary and the pilot-protocol daemon you will join to network 9, because queries and their text will be transmitted to remote agents and may be proxied to upstream services (the response envelope includes upstream_url). Do not send secrets, credentials, or highly sensitive personal data to these agents. If you plan to use premium services (e.g., Google Cloud Translate/TTS), confirm how and where those credentials are provided (they are not requested by this skill) and review the policies of any third-party LLM (Gemini) used for /summary. If you need stronger guarantees, ask for details about the pilot-protocol overlay participants and the provenance of the pilotctl binary before proceeding.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

Binspilotctl
latestvk9792mbp7er5457afghqzgyg1585qr00
28downloads
0stars
1versions
Updated 9h ago
v1.0.0
MIT-0

pilot-service-agents-language

Language and NLP services — translation, text-to-speech, dictionaries, word tools, Bible text, linguistic corpora.

All agents in this category follow the standard contract described in pilot-service-agents. Send /help to any agent to read its exact filter schema — the table below is a snapshot; the catalogue grows, so always verify with a fresh list-agents query.

Agents in this category (snapshot)

HostnameDescription
bible-apiBiblical text across translations
datamuse-sugDatamuse Sug
datamuse-wordsWord finder: rhymes, related, semantic
free-dictionary-enEnglish word definitions and phonetics
gcp-translateGoogle Cloud Translation (500K chars/mo free)
gcp-tts-voicesGoogle Text-to-Speech voice catalog
genderizePredict gender from first name
libretranslate-languagesLibretranslate Languages
mymemory-translateMyMemory machine translation (50+ languages)
nationalizePredict nationality from name
purgomalum-profanityProfanity/content filter for text moderation
quran-cloudQuranic text with translations
spellcheck-apiSpellcheck Api
urban-dictionaryCrowdsourced slang dictionary
wikimedia-langlinksWikimedia Langlinks
wiktionary-defineWiktionary Define

What you can expect

  • Google Cloud Translation (premium) + Text-to-Speech voice catalogue (premium)
  • Datamuse suggestions/words, Free Dictionary, Bible passages

What NOT to expect

  • OCR, speech recognition, or arbitrary generative text
  • Guaranteed dialect / register fidelity — upstreams vary

Commands (same pattern for every agent in the category)

# Read an agent's filter contract
pilotctl --json send-message <hostname> --data "/help"
pilotctl --json inbox

# Fetch structured data
pilotctl --json send-message <hostname> --data '/data {json filters}'
pilotctl --json inbox

# Natural-language summary (Gemini)
pilotctl --json send-message <hostname> --data '/summary {json filters}'
pilotctl --json inbox

Response shape

send-message returns an ACK envelope immediately ({"ack":"ACK TEXT N bytes", "bytes":N, "target":"<address>", "type":"text"}). The actual agent response arrives a few seconds later and is read with pilotctl --json inbox. Each inbox entry carries the agent's normalised envelope in its data field:

{
  "source": "<hostname>",
  "items":  [...],
  "count":  <int>,
  "total":  <int|null>,
  "page":   <int|null>,
  "next":   <cursor|null>,
  "truncated": <bool>,
  "upstream_url": "<resolved upstream URL>"
}

/help returns plain text. /summary returns a Gemini-generated prose string. Free-text queries also return Gemini prose.

Workflow Example

# 1. Fresh discovery — the catalogue grows, never hard-code
pilotctl --json send-message list-agents --data '/data {"category":"language","limit":20}'
pilotctl --json inbox

# 2. Read the contract of a specific agent
pilotctl --json send-message datamuse-words --data '/help'
pilotctl --json inbox

# 3. Query it
pilotctl --json send-message datamuse-words --data '/data {"ml":"ringing in the ears"}'
pilotctl --json inbox

Dependencies

Requires the pilot-protocol core skill, the pilot-service-agents skill (for the general discovery flow), pilotctl on PATH, and a running daemon joined to network 9.

Comments

Loading comments...