Get card
Download
question-intake@1.0.0.yamlClone
npx -y darkprint clone question-intake@1.0.0There is no repository and no history behind a card. Download hands you the document as it stands, and Clone fetches the same document by name.
Open a research run from an inbound question, carrying the asker's scope and deadline with it so every downstream strand knows what it is allowed to go looking for.
used in 3 blueprints
Specification
135 words · handed to the agentTake the oldest unhandled message from the research-desk-inbox source and turn it into one research question. Keep the asker's own wording for the ask itself, drop greetings, signatures and quoted reply chains, then append the scope they stated, date range, sources to prefer or avoid, and the deadline, as a short Scope: line beneath the question. Trim the result to at most 2000 characters, cutting at a sentence boundary rather than mid-word, and emit it as plain text on question. If the message carries more than one ask, keep the first and list the others verbatim under Also asked:; if it carries nothing that can be researched, emit nothing and end the run. You are done the moment one question with its scope has been emitted, do not answer it, rank it, or retrieve anything.
Interfaces
0 in · 1 outInputs
0No inputs declared, nothing upstream feeds this node.
Outputs
1| Name | Data type | Description |
|---|---|---|
| question | text | The question as asked, trimmed to a single stated ask with its scope attached. |
Dependencies
0None declared, no edge has to arrive for this node to run.
Card values
11 declaredWho the node is. The id is the key the DOT pins.
- id
- question-intake
- name
- Question Intake
- type
- tool
- phases
- none declared
What it does, and the prose the agent is handed when the graph runs.
- action29 words
- Open a research run from an inbound question, carrying the asker's scope and deadline with it so every downstream strand knows what it is allowed to go looking for.
- spec135 words
- Take the oldest unhandled message from the
research-desk-inboxsource and turn it into one research question. Keep the asker's own wording for the ask itself, drop greetings, signatures and quoted reply chains, then append the scope they stated, date range, sources to prefer or avoid, and the deadline, as a shortScope:line beneath the question. Trim the result to at most 2000 characters, cutting at a sentence boundary rather than mid-word, and emit it as plain text onquestion. If the message carries more than one ask, keep the first and list the others verbatim underAlso asked:; if it carries nothing that can be researched, emit nothing and end the run. You are done the moment one question with its scope has been emitted, do not answer it, rank it, or retrieve anything.in full above - model
- whatever the graph supplies
- agent
- not named
- skill
- skills/question-intake.md
- tools
- none
- mcp
- none
- params
- source: research-desk-inbox, max_question_chars: 2000
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- none
- outputs
- question : text
- dependencies
- none
- cannot
- no type is refused
- will_not
- answer the question it opens the run with, retrieve anything
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes
- none
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- question-intake@1.0.0currentsha256:d200653dffd614a96e979bf36b0afc71e0ef6e56d45b5c0d7441d5c62419960b
pinned byBudget Aware Router
autogen/budget-aware-router,Grounded Research Deskautogen/grounded-research-desk,Hypothesis Tournamentautogen/hypothesis-tournament
A digest is a fingerprint (SHA-256) of the card's content, computed without the author and provenance fields. The same card from two people gets the same digest; any edit gets a new one.
First published version, so there is nothing to compare yet. Versions are never edited in place: the next change arrives as a new version, and the differences between the two documents are listed here.
Community notes (0)
No notes yet.
Nobody has posted about this node card yet.
Sign in to post a note.