[agentrc readiness] AgentRC Readiness: Level 0 — Fix First gaps
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- typescript
- Domain
- build-system, devtools, testing-qa, tooling
Research direction
Start by checking the app's package.json for build and test scripts, then review the AgentRC readiness report at /tmp/gh-aw/agent/readiness-summary.md. Inspect whether .vscode/mcp.json or an Agent Plugin mcp.json is the appropriate MCP configuration location. Done means the app passes the build-script, test-script, and MCP-configuration readiness checks.
Written by the indexing model from the issue text.
Description
Readiness snapshot
| Metric | Result |
|---|---|
| Achieved level | Level 0 — Functional |
Highest-impact gaps
- Build script present (0/1 apps) — high impact, low effort
- Only 0/1 apps pass this check.
- Test script present (0/1 apps) — high impact, low effort
- Only 0/1 apps pass this check.
- MCP configuration present — high impact, low effort
- Missing MCP (Model Context Protocol) configuration (e.g. .vscode/mcp.json or an Agent Plugin mcp.json).
Recommended next step
Ask a maintainer to verify that a build script exists in the app's package.json (the report indicates 0/1 apps currently pass this check), since AgentRC did not provide an exact file/command for this repo.
Evidence
- /tmp/gh-aw/agent/readiness-summary.md (AgentRC readiness report)
Generated by AgentRC Readiness Report · copilot · auto · 9.27 AIC · ⌖ 4.98 AIC · ⊞ 6.3K · ◷
- expires on Oct 9, 2026, 5:33 AM UTC
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 94
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 34
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/agentrc
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 25/100
microsoft/agentrc#379 · 1 reaction ·
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/agentrc#372 · 1 reaction ·
Maintainers usually reply within 1 day
-
[aw] Detection RunsOpenagentic-workflows
Difficulty 5/5 Over a week Newbie friendliness 1/100
microsoft/agentrc#349 · 8 comments ·
Maintainers usually reply within 1 day
All issues in microsoft/agentrc
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
diegosouzapw/OmniRoute#14869 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
Maintainers usually reply within 1 day
-
status: waiting triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
freeCodeCamp/freeCodeCamp#70412 ·
Maintainers usually reply within 1 day
-
Mend: dependency security vulnerability untriaged
Difficulty 1/5 Under an hour Newbie friendliness 88/100
opensearch-project/OpenSearch-Dashboards#12816 ·
Maintainers usually reply within 1 day