Pilot translate
80+ agent skills for Pilot Protocol — communication, file transfer, trust, task routing, swarm coordination, and more
npx -y skills add TeoSlayer/pilot-skills --skill pilot-translateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Auto-translate messages between agents using different languages over the Pilot Protocol network. Use this skill when: 1. You need cross-language communication between agents 2. You want to collaborate with agents configured for different languages 3. You need multilingual message support Do NOT use this skill when: - All agents use the same language (use pilot-chat) - You need file transfer (use pilot-send-file) - You need raw untranslated messages (use pilot-chat)
The file declares its own license as AGPL-3.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.4 KB, as published. Nobody here has run it
pilot-translate
Auto-translate messages between agents using different languages. Enables seamless cross-language communication over Pilot Protocol.
Commands
Configure settings
# Set config values
pilotctl --json config --set language=<language-code>
pilotctl --json config --set auto-translate=true
Send message with manual translation
# Translate before sending (using external tool)
MESSAGE="Hello, how are you?"
TRANSLATED=$(echo "$MESSAGE" | translate-cli en es) # External tool
pilotctl --json send-message <hostname> --data "$TRANSLATED"
Receive messages
pilotctl --json inbox
View config
pilotctl --json config
Workflow Example
Agent A (English) and Agent B (Spanish) collaborate using external translation:
#!/bin/bash
# Agent A (English) - requires trans or similar tool
# Configure language preference
pilotctl --json config --set language=en
# Translate and send message
MESSAGE="Can you process the customer data from yesterday?"
TRANSLATED=$(echo "$MESSAGE" | trans en:es -brief)
pilotctl --json send-message agent-b --data "$TRANSLATED"
# Check inbox and translate responses
INBOX=$(pilotctl --json inbox)
echo "$INBOX" | jq -r '.items[]? | .content' | while read -r msg; do
echo "$msg" | trans es:en
done
#!/bin/bash
# Agent B (Spanish) - requires trans or similar tool
# Configure language preference
pilotctl --json config --set language=es
# Check inbox and translate to Spanish
INBOX=$(pilotctl --json inbox)
echo "$INBOX" | jq -r '.items[]? | .content' | while read -r msg; do
echo "$msg" | trans en:es
done
# Respond in Spanish (will be translated by recipient)
RESPONSE="Sí, comenzaré el procesamiento ahora. ETA: 30 minutos"
pilotctl --json send-message agent-a --data "$RESPONSE"
Language Codes
Common ISO 639-1 codes:
en— Englishes— Spanishfr— Frenchde— Germanzh— Chineseja— Japanesear— Arabicru— Russianpt— Portugueseit— Italian
Translation Tools
External translation tools (install separately):
- trans — Command-line Google Translate:
trans en:es "hello" - translate-shell — Alternative CLI translator
- DeepL API — High quality with API key
- LibreTranslate — Self-hosted open-source
Install trans:
# Linux/macOS
wget git.io/trans
chmod +x ./trans
sudo mv trans /usr/local/bin/
Dependencies
Requires pilot-protocol skill, pilotctl binary, running daemon, and external translation tool like trans.