REPOGEO REPORT · LITE

jnMetaCode/agency-orchestrator

Default branch main · commit 46152742 · scanned 5/29/2026, 3:12:09 AM

GitHub: 1,103 stars · 168 forks

AI VISIBILITY SCORE

33 /100

Critical

Category recall

0 / 2

Not recommended in any query

Rule findings

2 pass · 0 warn · 0 fail

Objective metadata checks

AI knows your name

2 / 3

Direct prompts that named your repo

HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface jnMetaCode/agency-orchestrator, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION

highreadme#1

Clarify core value proposition in README's opening

Why:

CURRENT

The current README starts with a Chinese headline and then a bulleted list of features.

COPY-PASTE FIX

Add a concise English sentence right after the main title, e.g., "Orchestrate multi-AI-role collaboration with a single sentence, generating complete plans in minutes using zero-code YAML and supporting 9 LLM providers."

mediumtopics#2

Add explicit topics for no-code and natural language orchestration

Why:

CURRENT

agent-orchestration, ai-agents, aider, autogen-alternative, claude, codex, copilot, crewai-alternative, cursor, deepseek, gemini-cli, langgraph-alternative, mcp-server, multi-agent, no-api-key, ollama, openai, orchestrator, workflow, yaml-workflow

COPY-PASTE FIX

agent-orchestration, ai-agents, aider, autogen-alternative, claude, codex, copilot, crewai-alternative, cursor, deepseek, gemini-cli, langgraph-alternative, mcp-server, multi-agent, no-api-key, ollama, openai, orchestrator, workflow, yaml-workflow, no-code, low-code, natural-language-processing, llm-orchestration, ai-workflow-automation

lowreadme#3

Expand "Why Agency Orchestrator" section with explicit differentiators

Why:

CURRENT

The README excerpt shows the section "## 为什么需要 Agency Orchestrator" ending abruptly with "跟一个 AI 聊天，它给你一个视".

COPY-PASTE FIX

Complete and expand the "Why Agency Orchestrator" section to explicitly highlight its unique advantages, such as "one-sentence input for complex tasks," "zero-code YAML configuration," "automatic role matching from 211+ experts," and "parallel DAG execution," contrasting these with typical multi-agent frameworks that require more manual setup or coding.

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall

0 / 2

0% of queries surface jnMetaCode/agency-orchestrator

Avg rank

—

Lower is better. #1 = top recommendation.

Share of voice

Of all named tools, what % are you?

Top rival

LangFlow

Recommended in 1 of 2 queries

COMPETITOR LEADERBOARD

LangFlow · recommended 1×
Chainlit · recommended 1×
Microsoft Copilot Studio · recommended 1×
Voiceflow · recommended 1×
Zapier · recommended 1×

CATEGORY QUERY
How to easily coordinate multiple AI agents for complex problem-solving without coding?
you: not recommended
AI recommended (in order):
1. LangFlow
2. Chainlit
3. Microsoft Copilot Studio
4. Voiceflow
5. Zapier
6. Make
7. Tavily AI
AI recommended 7 alternatives but never named jnMetaCode/agency-orchestrator. This is the gap to close.
Show full AI answer
CATEGORY QUERY
Seeking a tool to orchestrate AI workflows using natural language across various LLM providers.
you: not recommended
AI recommended (in order):
1. LangChain
2. LlamaIndex
3. Microsoft Semantic Kernel
4. Haystack
5. OpenAI Assistants API
6. CrewAI
AI recommended 6 alternatives but never named jnMetaCode/agency-orchestrator. This is the gap to close.
Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

Metadata completeness
pass
README presence
pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

Compared to common alternatives in this category, what is the core differentiator of jnMetaCode/agency-orchestrator?
pass
AI did not name jnMetaCode/agency-orchestrator — likely talking about a different project
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?
If a team adopts jnMetaCode/agency-orchestrator in production, what risks or prerequisites should they evaluate first?
pass
AI named jnMetaCode/agency-orchestrator explicitly
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?
In one sentence, what problem does the repo jnMetaCode/agency-orchestrator solve, and who is the primary audience?
pass
AI named jnMetaCode/agency-orchestrator explicitly
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of jnMetaCode/agency-orchestrator. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

Live preview

MARKDOWN (README)

[![RepoGEO](https://repogeo.com/badge/jnMetaCode/agency-orchestrator.svg)](https://repogeo.com/en/r/jnMetaCode/agency-orchestrator)

HTML

<a href="https://repogeo.com/en/r/jnMetaCode/agency-orchestrator"><img src="https://repogeo.com/badge/jnMetaCode/agency-orchestrator.svg" alt="RepoGEO" /></a>

Pro

Subscribe to Pro for deep diagnoses

jnMetaCode/agency-orchestrator — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

Deep reports10 / month
Brand-free category queries5 vs 2 in Lite
Prioritized action items8 vs 3 in Lite