feat: add text, seo, and translate tools - #852
Merged
avoidwork merged 7 commits intoAug 23, 2026
Merged
Conversation
Add proposal, design, specs, and tasks for three new tools: - text (copywriting, editing, summarization, rewriting) - seo (keyword density, meta descriptions) - translate (translation, language detection with caching)
Add three new text processing tools: - text: summarize, rewrite, tone adjustment, grammar correction, shorten/expand - seo: keyword density, meta description, SERP analysis, content optimization - translate: multi-language translation with language detection, caching, rate limiting Each tool follows the existing pattern: zod schema, impl function, registration. Translation uses google-translate-api with env var GOOGLE_TRANSLATE_API_KEY. Text and SEO tools use the existing LLM integration via ChatOpenAI. Input validation enforces 10,000 character limit across all tools. Translation includes tiny-lru caching (24h TTL) and rate limiting (10 req/s). Closes #784
Archive the completed change and sync spec deltas for: - text-processing: copywriting/editing operations - seo-analysis: SEO analysis operations - translation: translation and language detection
avoidwork
changed the title
Replace google-translate-api dependency with ChatOpenAI-based translation, consistent with text and seo tools. Removes external API key requirement — translate now uses the same OpenAI LLM as the other text processing tools. Closes #784
Replace \-\- with \-\- to properly escape double dashes in shell commands, preventing premature parsing by the shell command parser. Closes #784
Replace 3 tool-based implementations (text, seo, translate) with 3 dedicated subagents that use the same LLM infrastructure: - textEditor (Hannibal's precision): summarize, rewrite, tone, grammar, shorten, expand - seoAnalyst (Martin's curiosity): keyword-density, meta-description, SERP-analysis, optimize - translator (Hannibal's cultural sophistication): translate, detect Each subagent has its own system prompt in prompts/, a definition in src/agent/definitions/, and is registered in getAllAgents(). Temperatures configured in config.yaml: 0.4, 0.3, 0.3 respectively. Removed: src/tools/text.js, seo.js, translate.js and their tests. Updated: README.md subagent tables, config.yaml temperatures, agentDefinitions.test.js for 12 agents. Closes #784
Rewrite all 3 spec files to describe the subagent-based approach: - text-processing: textEditor subagent (summarize, rewrite, tone, grammar, shorten, expand) - seo-analysis: seoAnalyst subagent (keyword-density, meta-description, SERP-analysis, optimize) - translation: translator subagent (translate, detect) Also mark all verification tasks as complete in the archive tasks.md. Closes #784
avoidwork
deleted the
scan-issue-784-add-text-processing-and-content-generation-tools
branch
August 23, 2026 19:49
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Add three new text processing tools to the madz harness:
All tools follow the existing pattern: zod schema, impl function, registration in index.js. Structured JSON output from all tools for reliable agent parsing. Input validation enforces a 10,000 character limit across all tools.
Type of Change
Testing
Coverage
Checklist
Closes #784