Thanks @vasanth15-hts — great rewrite of the Security Engineer. The adversarial thinking framework and expanded STRIDE analysis are a real improvement.
Introduce a new Filament-focused agent for high-impact admin UX improvements.
Includes structural form redesign rules (tabs, grids, sliders, collapsible sections),
anti-cosmetic guardrails, and noise-reduction principles for straightforward inputs.
Engineering:
- Feishu Integration Developer (Feishu/Lark bots + approvals + Bitable)
Specialized:
- Study Abroad Advisor (multi-country application strategy)
- Government Digital Presales Consultant (China ToG market)
- Corporate Training Designer (ADDIE/SAM + enterprise learning)
- Healthcare Marketing Compliance (China medical ad law + NMPA)
From jnMetaCode/agency-agents-zh, translated to English.
OpenClaw support:
- Add section-splitting convert_openclaw() to convert.sh that routes
## headers by keyword into SOUL.md (persona) vs AGENTS.md (operations)
and generates IDENTITY.md with emoji + vibe from frontmatter
- Add integrations/openclaw/ to .gitignore
Frontmatter additions (all 112 agents):
- Add emoji and vibe fields to every agent for OpenClaw IDENTITY.md
generation and future dashboard/catalog use
- Add services field to carousel-growth-engine (Gemini API, Upload-Post)
- Add emoji/vibe to 7 new paid-media agents from PR #83
Agent quality:
- Rewrite accounts-payable-agent to be vendor-agnostic (remove AgenticBTC
dependency, use generic payments.* interface)
Documentation:
- CONTRIBUTING.md: Add Persona/Operations section grouping guidance,
emoji/vibe/services frontmatter fields, external services editorial policy
- README.md: Add OpenClaw to supported tools, update agent count to 112,
reduce third-party OpenClaw repo mention to one-line attribution
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Added comprehensive guidelines and responsibilities for the Data Engineer & ETL Architect role, including pipeline design, AI remediation, and compliance rules.
Three new specialist agents filling clear gaps in the current roster:
- engineering/engineering-data-engineer.md: ETL/ELT pipelines, Delta Lake,
Apache Spark, dbt, Medallion Architecture (Bronze/Silver/Gold), streaming
with Kafka, data quality with Great Expectations, cloud lakehouse platforms
(Fabric, Databricks, Synapse, Snowflake, BigQuery)
- engineering/engineering-technical-writer.md: Developer documentation,
API reference (OpenAPI), README templates, tutorials, docs-as-code
(Docusaurus/MkDocs), content quality standards, DX metrics
- specialized/specialized-developer-advocate.md: Developer relations,
DX auditing and improvement, technical content creation, community
building, GitHub engagement, conference talks, product feedback loops
Each agent follows the standard template with YAML frontmatter, identity,
core mission, critical rules, technical deliverables with working code,
workflow process, communication style, and success metrics.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Adds a specialized Security Engineer agent covering threat modeling,
vulnerability assessment, secure code review, and security architecture.
This fills a gap in the Engineering Division where no dedicated security
specialist existed.
Update 19 agent name: fields from slug-style (e.g. "engineering-ai-engineer")
or code-style (e.g. "ArchitectUX") to clean human-readable names (e.g.
"AI Engineer", "UX Architect"). Add missing YAML frontmatter to 2 spatial-
computing agents. All 51 agents now use consistent naming that aligns with
the NEXUS strategy docs.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Fix malformed YAML frontmatter with literal \n characters in agent files
- Fix insecure HTTP link in README (http:// -> https://)
- Update outdated year references (2024 -> 2025)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
