translate-synset-serbian

Translate English WordNet synsets to Serbian literals and glosses.

Updated Jul 14, 2025
One-click install
npx skills add https://github.com/sasa5linkar/wordnet_autotranslate- --skill translate-synset-serbian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: translate-synset-serbian
Source: https://github.com/sasa5linkar/wordnet_autotranslate-/tree/main/skills/translate-synset-serbian
Command: npx skills add https://github.com/sasa5linkar/wordnet_autotranslate- --skill translate-synset-serbian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides accurate Serbian translations for English WordNet synsets within Codex sessions using pure agent workflows or optional repo-backed Ollama comparisons.

Core Features & Use Cases

  • Pure agent workflows: agent-baseline, agent-multiphase, and agent-conceptual (and agent-all) to generate and validate translations.
  • Repo-backed options: optional repo-based pipelines for comparison and reproducibility.
  • Resolve synsets via ENG30 IDs, WordNet names, lemmas+POS, or payloads, enabling flexible inputs and batch processing.
  • Output formats: structured JSON payloads suitable for downstream curation and validation.

Quick Start

Invoke the skill with an ENG30 selector to translate a synset using the agent-all workflow for a ready Serbian gloss.

Frequently Asked Questions about translate-synset-serbian

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate English WordNet synsets to Serbian within an agent workflow?▼

You translate English WordNet synsets to Serbian by applying Codex-based agent workflows to ENG30 IDs, synset names, lemma+POS pairs, spreadsheets, or raw payloads to generate Serbian literals and glosses. The skill provides pure agent workflows like agent-baseline, agent-multiphase, and agent-conceptual.

What inputs are supported for resolving WordNet synsets during Serbian translation?▼

WordNet synsets can be resolved for Serbian translation using ENG30 IDs, WordNet names, lemma+POS pairs, spreadsheets, or raw payloads. This enables flexible inputs and batch processing for generating structured JSON payloads.

Do I need NLTK WordNet installed to use Serbian synset translation workflows?▼

Yes, NLTK WordNet is required for Serbian synset translation workflows. Optional LangGraph and Ollama dependencies can be added to enable repo-backed pipelines for comparison and reproducibility.

What is the difference between pure agent workflows and repo-backed options for Serbian WordNet translation?▼

Pure agent workflows generate and validate Serbian translations directly, while repo-backed options provide optional pipelines for comparison and reproducibility. Both output structured JSON payloads suitable for downstream curation.

Can I compare Ollama translations with agent-based Serbian WordNet outputs?▼

Yes, you can compare Ollama translations with agent outputs using optional repo-backed pipelines. The agent-all workflow combines baseline, multiphase, and conceptual approaches to produce validated Serbian glosses for comparison.

What output format does Serbian WordNet translation produce for downstream NLP tasks?▼

Serbian WordNet translation produces structured JSON payloads containing Serbian literals and glosses. These outputs are suitable for downstream curation, validation, and integration into NLP pipelines.