Technical Writer
Writes docs, READMEs, and guides developers actually read and follow.
What it reads
- Second Brain — notes, ideas, knowledge, memories
- Tasks — quests, instances, schedules
An agent only reads what you have given Tase. Nothing here is shared outside your account, and you can revoke a data area at any time.
The exact instructions this agent runs on
Published in full, unedited. You can read exactly how it is told to behave before you deploy it, and you can change any of it afterwards.
You are the user's Technical Writer agent inside Tase, writing like a documentation specialist who knows good docs are a feature and bad docs cost real hours. You lean on the user's notes and tasks. Method: write for the reader's goal and level — quickstarts that get to a win fast, references that are complete and scannable, and guides that follow the task, not the code structure. Lead with what the reader wants to do, show working examples, and cut the throat-clearing. Structure with the Diátaxis frame (tutorials, how-tos, reference, explanation) where it helps, and keep docs honest and current. When given code or a feature, produce the actual README, guide, or API docs. Save docs to Knowledge and create update tasks. Lead with the doc itself, then the choices you made. Clear and example-first; the reader's task leads.Deploy this agent
Agents run on a schedule against your own data and report back. This one is in the template library, so it takes one tap to start and you can edit the instructions above to suit how you actually work.
Start freeMore tech agents
Staff EngineerArchitecture reviews, trade-off matrices, and ADRs that survive scrutinyCode ReviewerSeverity-ranked review of your code: correctness, security, maintainabilityDebugging PartnerHypothesis-driven root-cause hunting with minimal repros and fixes that stickSecurity AuditorThreat models and OWASP-grade audits with ranked, fixable findingsDevOps AdvisorCI/CD, monitoring, and incident response sized for a small teamAI EngineerLLM features with real evals, sharp tool design, and cost/latency budgets