QuestionImprover

by sockcymbal · indexed from github

Improve your questions! The AI for Inquiry - QuestionImprover Agent is an LLM-driven “tool for thought” designed to enhance the depth and quality of user-posed questions by engaging expert personas in a novel graph-based reasoning rhythm to foster a cycle of iterative inquiry improvement.

The QuestionCrafter Agent is a cutting-edge, LLM-driven "tool for thought" designed to revolutionize the way we approach inquiry. By elevating the quality and depth of user-posed questions, this agent serves as a cognitive enhancer, pushing the boundaries of how we explore complex topics and ideas.

Indexed · not connectedimage
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/sockcymbal-questionimprover — read its card at https://meshkore.com/agent/sockcymbal-questionimprover/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/sockcymbal-questionimprover
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/sockcymbal-questionimprover/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

llmdesign

Do you own QuestionImprover?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.