Skip to content

level-3: Ritheeshwar K#459

Closed
Ritheeshwar wants to merge 0 commit intoLife-Atlas:masterfrom
Ritheeshwar:level3-final-clean
Closed

level-3: Ritheeshwar K#459
Ritheeshwar wants to merge 0 commit intoLife-Atlas:masterfrom
Ritheeshwar:level3-final-clean

Conversation

@Ritheeshwar
Copy link
Copy Markdown
Contributor

Submission Level

Level:3

What I Did

Built an intelligent agent that dynamically selects LPI tools based on user query intent.

Checklist

  • I read the README and CONTRIBUTING guide
  • My PR title follows the format
  • I tested my changes locally before submitting

Signed-off-by: Ritheeshwar K ritheeshwarkannan@gmail.com

@github-actions github-actions Bot added the level-3 Level 3: Shipping label Apr 21, 2026
@github-actions
Copy link
Copy Markdown
Contributor

🏆 Level 3 submission received. This is the one that counts.

An agent will clone your repo, attempt to run it, and evaluate your work. You'll receive a detailed score and feedback as a comment on this PR.

Completing Level 3 guarantees your place on the WINNIIO / LifeAtlas contributor team. Welcome to the real work.

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Level 3 Evaluation

Score: 3/13 ⭐⭐⭐☆☆ (23%)

Submission Document

✅ Agent repo linked: https://github.com/Ritheeshwar/lpi-smart-agent
⚠️ Write-up is thin (46 words)
❌ No LPI tools referenced
⚠️ No evidence of explainability
⚠️ HOW_I_DID_IT.md is too brief (31 words)

Repo Analysis

✅ Repo cloned successfully
✅ README present
❌ No evidence of LPI tool calls in code
⚠️ Minimal error handling (1 instances)

❓ Your code doesn't appear to call any LPI tools. The requirement is clear: 'Query at least 2 LPI tools.' How does your agent get data from the LPI?

❓ What happens if the LPI server is down? What if the user sends empty input? What if the LLM returns garbage? Try breaking your own agent and see what happens.

Questions for you

Please respond to these in a comment on this PR. We read every answer.
❓ If someone else submitted this exact write-up, what score would you give it? What's missing?

❓ The challenge requires querying at least 2 LPI tools. Which ones did you use, and what did they return?

❓ If a user asks your agent 'why did you recommend this?' — what does it say? Show us. Explainability isn't a feature, it's a requirement.

❓ What was the hardest part? What did you try that didn't work? That's what we want to read — the struggle, not the summary.

❓ What choices did you make that weren't in the instructions? What would you do differently next time? We're looking for people who think, not people who follow.

Verdict

Be honest with yourself. Does this submission reflect your best effort? If someone else submitted this, what score would you give it? Rework it and push again — the deadline is Sunday.


This is an automated evaluation. A human reviewer will follow up on all Level 3 submissions. Scores feed the leaderboard.

Tip: The best way to improve your score is to answer the questions above honestly and push an updated submission.

@github-actions
Copy link
Copy Markdown
Contributor

🏆 Level 3 submission received. This is the one that counts.

An agent will clone your repo, attempt to run it, and evaluate your work. You'll receive a detailed score and feedback as a comment on this PR.

Completing Level 3 guarantees your place on the WINNIIO / LifeAtlas contributor team. Welcome to the real work.

1 similar comment
@github-actions
Copy link
Copy Markdown
Contributor

🏆 Level 3 submission received. This is the one that counts.

An agent will clone your repo, attempt to run it, and evaluate your work. You'll receive a detailed score and feedback as a comment on this PR.

Completing Level 3 guarantees your place on the WINNIIO / LifeAtlas contributor team. Welcome to the real work.

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Level 3 Evaluation

Score: 4/13 ⭐⭐⭐⭐☆ (31%)

Submission Document

✅ Agent repo linked: https://github.com/Ritheeshwar/lpi-smart-agent
⚠️ Write-up is thin (89 words)
❌ No LPI tools referenced
⚠️ No evidence of explainability
✅ HOW_I_DID_IT.md present (108 words)

Repo Analysis

✅ Repo cloned successfully
✅ README present
❌ No evidence of LPI tool calls in code
⚠️ Minimal error handling (1 instances)

❓ Your code doesn't appear to call any LPI tools. The requirement is clear: 'Query at least 2 LPI tools.' How does your agent get data from the LPI?

❓ What happens if the LPI server is down? What if the user sends empty input? What if the LLM returns garbage? Try breaking your own agent and see what happens.

Questions for you

Please respond to these in a comment on this PR. We read every answer.
❓ If someone else submitted this exact write-up, what score would you give it? What's missing?

❓ The challenge requires querying at least 2 LPI tools. Which ones did you use, and what did they return?

❓ If a user asks your agent 'why did you recommend this?' — what does it say? Show us. Explainability isn't a feature, it's a requirement.

❓ What choices did you make that weren't in the instructions? What would you do differently next time? We're looking for people who think, not people who follow.

Verdict

Be honest with yourself. Does this submission reflect your best effort? If someone else submitted this, what score would you give it? Rework it and push again — the deadline is Sunday.


This is an automated evaluation. A human reviewer will follow up on all Level 3 submissions. Scores feed the leaderboard.

Tip: The best way to improve your score is to answer the questions above honestly and push an updated submission.

@github-actions
Copy link
Copy Markdown
Contributor

🏆 Level 3 submission received. This is the one that counts.

An agent will clone your repo, attempt to run it, and evaluate your work. You'll receive a detailed score and feedback as a comment on this PR.

Completing Level 3 guarantees your place on the WINNIIO / LifeAtlas contributor team. Welcome to the real work.

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Level 3 Evaluation

Score: 4/13 ⭐⭐⭐⭐☆ (31%)

Submission Document

✅ Agent repo linked: https://github.com/Ritheeshwar/lpi-smart-agent
⚠️ Write-up is thin (89 words)
❌ No LPI tools referenced
⚠️ No evidence of explainability
✅ HOW_I_DID_IT.md present (108 words)

Repo Analysis

✅ Repo cloned successfully
✅ README present
❌ No evidence of LPI tool calls in code
⚠️ Minimal error handling (1 instances)

❓ Your code doesn't appear to call any LPI tools. The requirement is clear: 'Query at least 2 LPI tools.' How does your agent get data from the LPI?

❓ What happens if the LPI server is down? What if the user sends empty input? What if the LLM returns garbage? Try breaking your own agent and see what happens.

Questions for you

Please respond to these in a comment on this PR. We read every answer.
❓ If someone else submitted this exact write-up, what score would you give it? What's missing?

❓ The challenge requires querying at least 2 LPI tools. Which ones did you use, and what did they return?

❓ If a user asks your agent 'why did you recommend this?' — what does it say? Show us. Explainability isn't a feature, it's a requirement.

❓ What choices did you make that weren't in the instructions? What would you do differently next time? We're looking for people who think, not people who follow.

Verdict

Be honest with yourself. Does this submission reflect your best effort? If someone else submitted this, what score would you give it? Rework it and push again — the deadline is Sunday.


This is an automated evaluation. A human reviewer will follow up on all Level 3 submissions. Scores feed the leaderboard.

Tip: The best way to improve your score is to answer the questions above honestly and push an updated submission.

@github-actions
Copy link
Copy Markdown
Contributor

🏆 Level 3 submission received. This is the one that counts.

An agent will clone your repo, attempt to run it, and evaluate your work. You'll receive a detailed score and feedback as a comment on this PR.

Completing Level 3 guarantees your place on the WINNIIO / LifeAtlas contributor team. Welcome to the real work.

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Level 3 Evaluation

Score: 4/13 ⭐⭐⭐⭐☆ (31%)

Submission Document

✅ Agent repo linked: https://github.com/Ritheeshwar/lpi-smart-agent
⚠️ Write-up is thin (89 words)
❌ No LPI tools referenced
⚠️ No evidence of explainability
✅ HOW_I_DID_IT.md present (108 words)

Repo Analysis

✅ Repo cloned successfully
✅ README present
❌ No evidence of LPI tool calls in code
⚠️ Minimal error handling (1 instances)

❓ Your code doesn't appear to call any LPI tools. The requirement is clear: 'Query at least 2 LPI tools.' How does your agent get data from the LPI?

❓ What happens if the LPI server is down? What if the user sends empty input? What if the LLM returns garbage? Try breaking your own agent and see what happens.

Questions for you

Please respond to these in a comment on this PR. We read every answer.
❓ If someone else submitted this exact write-up, what score would you give it? What's missing?

❓ The challenge requires querying at least 2 LPI tools. Which ones did you use, and what did they return?

❓ If a user asks your agent 'why did you recommend this?' — what does it say? Show us. Explainability isn't a feature, it's a requirement.

❓ What choices did you make that weren't in the instructions? What would you do differently next time? We're looking for people who think, not people who follow.

Verdict

Be honest with yourself. Does this submission reflect your best effort? If someone else submitted this, what score would you give it? Rework it and push again — the deadline is Sunday.


This is an automated evaluation. A human reviewer will follow up on all Level 3 submissions. Scores feed the leaderboard.

Tip: The best way to improve your score is to answer the questions above honestly and push an updated submission.

@github-actions
Copy link
Copy Markdown
Contributor

🏆 Level 3 submission received. This is the one that counts.

An agent will clone your repo, attempt to run it, and evaluate your work. You'll receive a detailed score and feedback as a comment on this PR.

Completing Level 3 guarantees your place on the WINNIIO / LifeAtlas contributor team. Welcome to the real work.

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Level 3 Evaluation

Score: 6/13 ⭐⭐⭐⭐⭐ (46%)

Submission Document

✅ Agent repo linked: https://github.com/Ritheeshwar/lpi-smart-agent
✅ Detailed write-up (144 words)
❌ No LPI tools referenced
✅ Explainability present — the agent shows its reasoning
✅ HOW_I_DID_IT.md present (108 words)

Repo Analysis

✅ Repo cloned successfully
✅ README present
❌ No evidence of LPI tool calls in code
⚠️ Minimal error handling (1 instances)

❓ Your code doesn't appear to call any LPI tools. The requirement is clear: 'Query at least 2 LPI tools.' How does your agent get data from the LPI?

❓ What happens if the LPI server is down? What if the user sends empty input? What if the LLM returns garbage? Try breaking your own agent and see what happens.

Questions for you

Please respond to these in a comment on this PR. We read every answer.
❓ The challenge requires querying at least 2 LPI tools. Which ones did you use, and what did they return?

❓ What choices did you make that weren't in the instructions? What would you do differently next time? We're looking for people who think, not people who follow.

Verdict

Needs more work. Read the questions below carefully. We're not trying to catch you out — we genuinely want to see you succeed. But we need to see real work, not surface-level output.


This is an automated evaluation. A human reviewer will follow up on all Level 3 submissions. Scores feed the leaderboard.

Tip: The best way to improve your score is to answer the questions above honestly and push an updated submission.

1 similar comment
@github-actions
Copy link
Copy Markdown
Contributor

🤖 Level 3 Evaluation

Score: 6/13 ⭐⭐⭐⭐⭐ (46%)

Submission Document

✅ Agent repo linked: https://github.com/Ritheeshwar/lpi-smart-agent
✅ Detailed write-up (144 words)
❌ No LPI tools referenced
✅ Explainability present — the agent shows its reasoning
✅ HOW_I_DID_IT.md present (108 words)

Repo Analysis

✅ Repo cloned successfully
✅ README present
❌ No evidence of LPI tool calls in code
⚠️ Minimal error handling (1 instances)

❓ Your code doesn't appear to call any LPI tools. The requirement is clear: 'Query at least 2 LPI tools.' How does your agent get data from the LPI?

❓ What happens if the LPI server is down? What if the user sends empty input? What if the LLM returns garbage? Try breaking your own agent and see what happens.

Questions for you

Please respond to these in a comment on this PR. We read every answer.
❓ The challenge requires querying at least 2 LPI tools. Which ones did you use, and what did they return?

❓ What choices did you make that weren't in the instructions? What would you do differently next time? We're looking for people who think, not people who follow.

Verdict

Needs more work. Read the questions below carefully. We're not trying to catch you out — we genuinely want to see you succeed. But we need to see real work, not surface-level output.


This is an automated evaluation. A human reviewer will follow up on all Level 3 submissions. Scores feed the leaderboard.

Tip: The best way to improve your score is to answer the questions above honestly and push an updated submission.

@github-actions
Copy link
Copy Markdown
Contributor

🏆 Level 3 submission received. This is the one that counts.

An agent will clone your repo, attempt to run it, and evaluate your work. You'll receive a detailed score and feedback as a comment on this PR.

Completing Level 3 guarantees your place on the WINNIIO / LifeAtlas contributor team. Welcome to the real work.

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Level 3 Evaluation

Score: 6/13 ⭐⭐⭐⭐⭐ (46%)

Submission Document

✅ Agent repo linked: https://github.com/Ritheeshwar/lpi-smart-agent
✅ Detailed write-up (144 words)
❌ No LPI tools referenced
✅ Explainability present — the agent shows its reasoning
✅ HOW_I_DID_IT.md present (222 words)

Repo Analysis

✅ Repo cloned successfully
✅ README present
❌ No evidence of LPI tool calls in code
⚠️ Minimal error handling (1 instances)

❓ Your code doesn't appear to call any LPI tools. The requirement is clear: 'Query at least 2 LPI tools.' How does your agent get data from the LPI?

❓ What happens if the LPI server is down? What if the user sends empty input? What if the LLM returns garbage? Try breaking your own agent and see what happens.

Questions for you

Please respond to these in a comment on this PR. We read every answer.
❓ The challenge requires querying at least 2 LPI tools. Which ones did you use, and what did they return?

❓ What choices did you make that weren't in the instructions? What would you do differently next time? We're looking for people who think, not people who follow.

Verdict

Needs more work. Read the questions below carefully. We're not trying to catch you out — we genuinely want to see you succeed. But we need to see real work, not surface-level output.


This is an automated evaluation. A human reviewer will follow up on all Level 3 submissions. Scores feed the leaderboard.

Tip: The best way to improve your score is to answer the questions above honestly and push an updated submission.

@github-actions
Copy link
Copy Markdown
Contributor

🏆 Level 3 submission received. This is the one that counts.

An agent will clone your repo, attempt to run it, and evaluate your work. You'll receive a detailed score and feedback as a comment on this PR.

Completing Level 3 guarantees your place on the WINNIIO / LifeAtlas contributor team. Welcome to the real work.

1 similar comment
@github-actions
Copy link
Copy Markdown
Contributor

🏆 Level 3 submission received. This is the one that counts.

An agent will clone your repo, attempt to run it, and evaluate your work. You'll receive a detailed score and feedback as a comment on this PR.

Completing Level 3 guarantees your place on the WINNIIO / LifeAtlas contributor team. Welcome to the real work.

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Level 3 Evaluation

Score: 6/13 ⭐⭐⭐⭐⭐ (46%)

Submission Document

✅ Agent repo linked: https://github.com/Ritheeshwar/lpi-smart-agent
✅ Detailed write-up (144 words)
❌ No LPI tools referenced
✅ Explainability present — the agent shows its reasoning
✅ HOW_I_DID_IT.md present (185 words)

Repo Analysis

✅ Repo cloned successfully
✅ README present
❌ No evidence of LPI tool calls in code
⚠️ Minimal error handling (1 instances)

❓ Your code doesn't appear to call any LPI tools. The requirement is clear: 'Query at least 2 LPI tools.' How does your agent get data from the LPI?

❓ What happens if the LPI server is down? What if the user sends empty input? What if the LLM returns garbage? Try breaking your own agent and see what happens.

Questions for you

Please respond to these in a comment on this PR. We read every answer.
❓ The challenge requires querying at least 2 LPI tools. Which ones did you use, and what did they return?

❓ What choices did you make that weren't in the instructions? What would you do differently next time? We're looking for people who think, not people who follow.

Verdict

Needs more work. Read the questions below carefully. We're not trying to catch you out — we genuinely want to see you succeed. But we need to see real work, not surface-level output.


This is an automated evaluation. A human reviewer will follow up on all Level 3 submissions. Scores feed the leaderboard.

Tip: The best way to improve your score is to answer the questions above honestly and push an updated submission.

@github-actions
Copy link
Copy Markdown
Contributor

🏆 Level 3 submission received. This is the one that counts.

An agent will clone your repo, attempt to run it, and evaluate your work. You'll receive a detailed score and feedback as a comment on this PR.

Completing Level 3 guarantees your place on the WINNIIO / LifeAtlas contributor team. Welcome to the real work.

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Level 3 Evaluation

Score: 6/13 ⭐⭐⭐⭐⭐ (46%)

Submission Document

✅ Agent repo linked: https://github.com/Ritheeshwar/lpi-smart-agent
✅ Detailed write-up (144 words)
❌ No LPI tools referenced
✅ Explainability present — the agent shows its reasoning
✅ HOW_I_DID_IT.md present (185 words)

Repo Analysis

✅ Repo cloned successfully
✅ README present
❌ No evidence of LPI tool calls in code
⚠️ Minimal error handling (1 instances)

❓ Your code doesn't appear to call any LPI tools. The requirement is clear: 'Query at least 2 LPI tools.' How does your agent get data from the LPI?

❓ What happens if the LPI server is down? What if the user sends empty input? What if the LLM returns garbage? Try breaking your own agent and see what happens.

Questions for you

Please respond to these in a comment on this PR. We read every answer.
❓ The challenge requires querying at least 2 LPI tools. Which ones did you use, and what did they return?

❓ What choices did you make that weren't in the instructions? What would you do differently next time? We're looking for people who think, not people who follow.

Verdict

Needs more work. Read the questions below carefully. We're not trying to catch you out — we genuinely want to see you succeed. But we need to see real work, not surface-level output.


This is an automated evaluation. A human reviewer will follow up on all Level 3 submissions. Scores feed the leaderboard.

Tip: The best way to improve your score is to answer the questions above honestly and push an updated submission.

@github-actions
Copy link
Copy Markdown
Contributor

🏆 Level 3 submission received. This is the one that counts.

An agent will clone your repo, attempt to run it, and evaluate your work. You'll receive a detailed score and feedback as a comment on this PR.

Completing Level 3 guarantees your place on the WINNIIO / LifeAtlas contributor team. Welcome to the real work.

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Level 3 Evaluation

Score: 6/13 ⭐⭐⭐⭐⭐ (46%)

Submission Document

✅ Agent repo linked: https://github.com/Ritheeshwar/lpi-smart-agent
✅ Detailed write-up (144 words)
❌ No LPI tools referenced
✅ Explainability present — the agent shows its reasoning
✅ HOW_I_DID_IT.md present (185 words)

Repo Analysis

✅ Repo cloned successfully
✅ README present
❌ No evidence of LPI tool calls in code
⚠️ Minimal error handling (1 instances)

❓ Your code doesn't appear to call any LPI tools. The requirement is clear: 'Query at least 2 LPI tools.' How does your agent get data from the LPI?

❓ What happens if the LPI server is down? What if the user sends empty input? What if the LLM returns garbage? Try breaking your own agent and see what happens.

Questions for you

Please respond to these in a comment on this PR. We read every answer.
❓ The challenge requires querying at least 2 LPI tools. Which ones did you use, and what did they return?

❓ What choices did you make that weren't in the instructions? What would you do differently next time? We're looking for people who think, not people who follow.

Verdict

Needs more work. Read the questions below carefully. We're not trying to catch you out — we genuinely want to see you succeed. But we need to see real work, not surface-level output.


This is an automated evaluation. A human reviewer will follow up on all Level 3 submissions. Scores feed the leaderboard.

Tip: The best way to improve your score is to answer the questions above honestly and push an updated submission.

1 similar comment
@github-actions
Copy link
Copy Markdown
Contributor

🤖 Level 3 Evaluation

Score: 6/13 ⭐⭐⭐⭐⭐ (46%)

Submission Document

✅ Agent repo linked: https://github.com/Ritheeshwar/lpi-smart-agent
✅ Detailed write-up (144 words)
❌ No LPI tools referenced
✅ Explainability present — the agent shows its reasoning
✅ HOW_I_DID_IT.md present (185 words)

Repo Analysis

✅ Repo cloned successfully
✅ README present
❌ No evidence of LPI tool calls in code
⚠️ Minimal error handling (1 instances)

❓ Your code doesn't appear to call any LPI tools. The requirement is clear: 'Query at least 2 LPI tools.' How does your agent get data from the LPI?

❓ What happens if the LPI server is down? What if the user sends empty input? What if the LLM returns garbage? Try breaking your own agent and see what happens.

Questions for you

Please respond to these in a comment on this PR. We read every answer.
❓ The challenge requires querying at least 2 LPI tools. Which ones did you use, and what did they return?

❓ What choices did you make that weren't in the instructions? What would you do differently next time? We're looking for people who think, not people who follow.

Verdict

Needs more work. Read the questions below carefully. We're not trying to catch you out — we genuinely want to see you succeed. But we need to see real work, not surface-level output.


This is an automated evaluation. A human reviewer will follow up on all Level 3 submissions. Scores feed the leaderboard.

Tip: The best way to improve your score is to answer the questions above honestly and push an updated submission.

@github-actions
Copy link
Copy Markdown
Contributor

🏆 Level 3 submission received. This is the one that counts.

An agent will clone your repo, attempt to run it, and evaluate your work. You'll receive a detailed score and feedback as a comment on this PR.

Completing Level 3 guarantees your place on the WINNIIO / LifeAtlas contributor team. Welcome to the real work.

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Level 3 Evaluation

Score: 6/13 ⭐⭐⭐⭐⭐ (46%)

Submission Document

✅ Agent repo linked: https://github.com/Ritheeshwar/lpi-smart-agent
✅ Detailed write-up (144 words)
❌ No LPI tools referenced
✅ Explainability present — the agent shows its reasoning
✅ HOW_I_DID_IT.md present (185 words)

Repo Analysis

✅ Repo cloned successfully
✅ README present
❌ No evidence of LPI tool calls in code
⚠️ Minimal error handling (1 instances)

❓ Your code doesn't appear to call any LPI tools. The requirement is clear: 'Query at least 2 LPI tools.' How does your agent get data from the LPI?

❓ What happens if the LPI server is down? What if the user sends empty input? What if the LLM returns garbage? Try breaking your own agent and see what happens.

Questions for you

Please respond to these in a comment on this PR. We read every answer.
❓ The challenge requires querying at least 2 LPI tools. Which ones did you use, and what did they return?

❓ What choices did you make that weren't in the instructions? What would you do differently next time? We're looking for people who think, not people who follow.

Verdict

Needs more work. Read the questions below carefully. We're not trying to catch you out — we genuinely want to see you succeed. But we need to see real work, not surface-level output.


This is an automated evaluation. A human reviewer will follow up on all Level 3 submissions. Scores feed the leaderboard.

Tip: The best way to improve your score is to answer the questions above honestly and push an updated submission.

@github-actions
Copy link
Copy Markdown
Contributor

🏆 Level 3 submission received. This is the one that counts.

An agent will clone your repo, attempt to run it, and evaluate your work. You'll receive a detailed score and feedback as a comment on this PR.

Completing Level 3 guarantees your place on the WINNIIO / LifeAtlas contributor team. Welcome to the real work.

@LifeAtlas
Copy link
Copy Markdown
Contributor

Hi Ritheeshwar,

Thanks for reaching out — I've reviewed your PR and the evaluation workflow in detail. The bot is functioning correctly, but I found a few items that need fixing on your end:

  1. File naming: Your submission is named submission.md — the evaluation workflow searches for level3.md. All passing L3 submissions use that exact filename. Please rename it.

  2. HOW_I_DID_IT.md is empty: The file exists but is 0 bytes. The evaluator requires at least 50 words of reflection on your process, challenges, and decisions.

  3. Tool output evidence: Your level3.md mentions tool names but doesn't include any actual output or responses from the LPI tools. The evaluator looks for real evidence that tools were called (e.g. sample responses, output snippets).

Fix these three items and push to your branch — the evaluation will re-trigger automatically.

Happy to help if you have questions.

— Life Atlas Program Team

@Ritheeshwar
Copy link
Copy Markdown
Contributor Author

Ritheeshwar commented Apr 22, 2026 via email

@github-actions
Copy link
Copy Markdown
Contributor

🏆 Level 3 submission received. This is the one that counts.

An agent will clone your repo, attempt to run it, and evaluate your work. You'll receive a detailed score and feedback as a comment on this PR.

Completing Level 3 guarantees your place on the WINNIIO / LifeAtlas contributor team. Welcome to the real work.

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Level 3 Evaluation

Score: 4/13 ⭐⭐⭐⭐☆ (31%)

Submission Document

✅ Agent repo linked: https://github.com/Ritheeshwar/lpi-smart-agent
⚠️ Write-up is thin (92 words)
❌ No LPI tools referenced
⚠️ No evidence of explainability
✅ HOW_I_DID_IT.md present (185 words)

Repo Analysis

✅ Repo cloned successfully
✅ README present
❌ No evidence of LPI tool calls in code
⚠️ Minimal error handling (1 instances)

❓ Your code doesn't appear to call any LPI tools. The requirement is clear: 'Query at least 2 LPI tools.' How does your agent get data from the LPI?

❓ What happens if the LPI server is down? What if the user sends empty input? What if the LLM returns garbage? Try breaking your own agent and see what happens.

Questions for you

Please respond to these in a comment on this PR. We read every answer.
❓ If someone else submitted this exact write-up, what score would you give it? What's missing?

❓ The challenge requires querying at least 2 LPI tools. Which ones did you use, and what did they return?

❓ If a user asks your agent 'why did you recommend this?' — what does it say? Show us. Explainability isn't a feature, it's a requirement.

❓ What choices did you make that weren't in the instructions? What would you do differently next time? We're looking for people who think, not people who follow.

Verdict

Be honest with yourself. Does this submission reflect your best effort? If someone else submitted this, what score would you give it? Rework it and push again — the deadline is Sunday.


This is an automated evaluation. A human reviewer will follow up on all Level 3 submissions. Scores feed the leaderboard.

Tip: The best way to improve your score is to answer the questions above honestly and push an updated submission.

@github-actions
Copy link
Copy Markdown
Contributor

This PR deletes existing files from the repo. That's not allowed — your PR should only ADD your own files.

Please:

  1. Re-fork the repo (or sync your fork with upstream)
  2. Only add your contributor JSON to contributors/
  3. Don't delete or modify other people's files

This PR will NOT be auto-merged. Fix it and push again.

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Level 3 Evaluation

Score: 6/13 ⭐⭐⭐⭐⭐ (46%)

Submission Document

✅ Agent repo linked: https://github.com/Ritheeshwar/lpi-smart-agent
✅ Detailed write-up (113 words)
✅ LPI tools referenced with evidence of actual output
⚠️ No evidence of explainability
✅ HOW_I_DID_IT.md present (95 words)

Repo Analysis

✅ Repo cloned successfully
✅ README present
❌ No evidence of LPI tool calls in code
⚠️ Minimal error handling (1 instances)

❓ Your code doesn't appear to call any LPI tools. The requirement is clear: 'Query at least 2 LPI tools.' How does your agent get data from the LPI?

❓ What happens if the LPI server is down? What if the user sends empty input? What if the LLM returns garbage? Try breaking your own agent and see what happens.

Questions for you

Please respond to these in a comment on this PR. We read every answer.
❓ If a user asks your agent 'why did you recommend this?' — what does it say? Show us. Explainability isn't a feature, it's a requirement.

❓ What choices did you make that weren't in the instructions? What would you do differently next time? We're looking for people who think, not people who follow.

Verdict

Needs more work. Read the questions below carefully. We're not trying to catch you out — we genuinely want to see you succeed. But we need to see real work, not surface-level output.


This is an automated evaluation. A human reviewer will follow up on all Level 3 submissions. Scores feed the leaderboard.

Tip: The best way to improve your score is to answer the questions above honestly and push an updated submission.

@github-actions
Copy link
Copy Markdown
Contributor

🏆 Level 3 submission received. This is the one that counts.

An agent will clone your repo, attempt to run it, and evaluate your work. You'll receive a detailed score and feedback as a comment on this PR.

Completing Level 3 guarantees your place on the WINNIIO / LifeAtlas contributor team. Welcome to the real work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

level-3 Level 3: Shipping

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants