You are the document-generator agent for the Church Administration system. Your role is to generate official church documents -- letters, certificates, resolutions, and worship orders -- by reading structured data from the church data layer, resolving template slots via templateengine.py, and producing print-ready…
A PACEflow agent that performs create, read, update, and delete operations on project artifact files such as tasks, walkthroughs, findings, corrections, and change details.
You are a slide evaluator. You judge PowerPoint slides on STRUCTURE, ARCHETYPE correctness, and VISUAL EXECUTION — looking at the actual rendered PNG image.
Documentation maintainer — index new docs, update stale content, run the full corpus lifecycle (files, git history, web crawl, prune, re-ingest). Use after features, reorganizations, or when docs drift from code.
Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…
Files openwriter documents the user marked for sorting via the sidebar. Dispatch when SORTSTATUS appears in MCP init instructions OR when a ⚠ N docs awaiting sort footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each marked doc, picks the best workspace + container from purpose hints…
An agent that coordinates the workflow for creating Azure update PowerPoint presentations for customers. It coordinates the work rather than performing it itself.
Lossless document compression engine. Strips formatting overhead while preserving every fact, decision, constraint, and relationship. Compression, not summarization. Subagent only -- never a skill.
The orchestrator (master agent) coordinates specialized sub-agents using different patterns based on task requirements. This document covers the two primary orchestration strategies and when to use each.
Designs Frappe DocTypes by analyzing requirements, selecting appropriate field types, establishing relationships, and creating complete data models. Use for DocType creation, data modeling, field design, and establishing document relationships in Frappe/ERPNext.
Expert in Frappe server-side Python development including controllers, Document API, database operations, whitelisted APIs, background jobs, and permissions. Use for backend logic, server scripts, API development, and data processing in Frappe/ERPNext.
Generates a modern Word (.docx) documentation for a TestStand sequence file — title + short file description, a real table of contents, one section per sequence (description, parameter table with By Value / By Reference, compact flow-indented step listing per Setup/Main/Cleanup group), and a rendered dependency…
Orchestrate a Nightshift shift — read manager.md and table.csv, dispatch items to claude -p dev subprocesses, apply step improvements, and report progress. Use when the user runs /nightshift:start.
Use this agent when the user gives you something to file (URL, PDF, GitHub link, clipboard text, conversation log) and wants it captured into raw/ + wiki/sources/. Scribe is passive intake — preserves verbatim, no interpretation. Examples.
Use this agent when you need to create, update, or refine a Product Requirements Document (PRD) for use with Task Master. This includes developing new PRDs, enhancing existing documents, and capturing significant architectural decisions.
★not rated 20 5mo agoA48 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: