feat: Add AI Startup Idea Validator#199
Open
dheeraj1029 wants to merge 18 commits into
Open
Conversation
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughThis PR adds a new “AI Startup Idea Validator” kit with kit metadata, flow wiring, model config, prompt templates, constitution rules, and documentation. ChangesAI Startup Idea Validator kit
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
:robot_face: AgentKit Structural ValidationNew Contributions Detected
Check Results
|
Contributor
|
Failure recorded at 2026-07-08T15:50:37Z UTC. If this PR is not fixed within 4 weeks it will be automatically closed. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 6
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@kits/ai-startup-idea-validator/agent.md`:
- Around line 1-3: Replace the placeholder TODO in agent.md with real agent
documentation for the AI Startup Idea Validator, including the agent’s identity,
purpose, capabilities, workflow/flow description, guardrails, and any
integration reference. Update the markdown content itself so the file is no
longer a stub and clearly documents the intended role and behavior of this kit’s
agent.
In `@kits/ai-startup-idea-validator/constitutions/default.md`:
- Around line 1-17: The markdown spacing fix needs to be applied in the source
template that generates the constitution, not only in the checked-in default
constitution file. Update the template/emitter responsible for producing the
default constitution so each heading such as Identity, Safety, Data Handling,
and Tone is surrounded by blank lines, and then regenerate the output so the
auto-generated kits stay lint-clean.
In `@kits/ai-startup-idea-validator/lamatic.config.ts`:
- Around line 11-15: The ai-startup-idea-validator step is missing the envKey
required by orchestrate.ts flow resolution, so add envKey to the step object in
lamaticConfig.steps for ai-startup-idea-validator and ensure it matches the
environment variable name used by deployment. Keep the change localized to the
step definition in lamatic.config.ts so the orchestrator can resolve it without
throwing.
In
`@kits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_system_0.md`:
- Around line 1-31: The prompt markdown in
ai-startup-idea-validator_llmnode-585_system_0.md should be normalized to
satisfy markdownlint: convert the opening prose into a proper heading and change
the section list in the prompt to use the repo’s expected repeated 1. style
instead of 2.-8. Update the prompt text while keeping the same content and
structure so the markdown in the prompt file passes CI linting.
In
`@kits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_user_1.md`:
- Around line 1-2: The prompt in the ai-startup-idea-validator user template is
pulling the startup idea from the wrong placeholder, so the model may never
receive the trigger text. Update the prompt to use the chat-trigger contract’s
actual output path instead of {{trigger.message}}, matching the pattern used by
knowledge-chatbot_rag_user.md and rag-chatbot.ts so the startup idea text is
passed through correctly.
In `@kits/ai-startup-idea-validator/README.md`:
- Around line 1-20: The README for the AI Startup Idea Validator is currently
just a feature summary, but kits/*/README.md needs to be a human-readable setup
guide and is still failing MD022/MD047. Update the README to follow the expected
setup-guide structure by adding clear install, configuration, and run steps, and
ensure the markdown has proper heading spacing and ends with a final newline.
Use the existing AI Startup Idea Validator README content as the starting point
and revise it into a step-by-step guide.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: ASSERTIVE
Plan: Pro
Run ID: 7f6ca96c-401c-4054-b62e-683acfda74a0
📒 Files selected for processing (10)
kits/ai-startup-idea-validator/.gitignorekits/ai-startup-idea-validator/README.mdkits/ai-startup-idea-validator/agent.mdkits/ai-startup-idea-validator/constitutions/default.mdkits/ai-startup-idea-validator/flows/ai-startup-idea-validator.tskits/ai-startup-idea-validator/lamatic.config.tskits/ai-startup-idea-validator/model-configs/ai-startup-idea-validator_llmnode-585_generative-model-name.tskits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_system_0.mdkits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_user_1.mdkits/smart-trip-itinerary-planner/prompts/smart-trip-itinerary-planner_llmnode-159_user_1.md
Contributor
There was a problem hiding this comment.
Actionable comments posted: 5
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
kits/ai-startup-idea-validator/flows/ai-startup-idea-validator.ts (1)
4-16: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winPopulate the flow metadata instead of leaving template defaults.
description,tags,githubUrl,documentationUrl,deployUrl, andauthor.emailare still blank here. If this export is surfaced anywhere, the kit will publish as an incomplete stub.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@kits/ai-startup-idea-validator/flows/ai-startup-idea-validator.ts` around lines 4 - 16, The flow metadata in meta is still using template defaults, so populate the missing fields instead of leaving them blank. Update the AI Startup Idea Validator meta export to provide meaningful values for description, tags, githubUrl, documentationUrl, deployUrl, and author.email, keeping the existing meta object structure intact so the flow is published with complete information.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@kits/ai-startup-idea-validator/agent.md`:
- Line 67: The markdown file is missing a trailing newline at EOF, which
triggers markdownlint MD047. Update the agent.md content so it ends cleanly with
a final newline after the last line, keeping the existing “Recommendations for
improvement” section and surrounding content unchanged.
- Line 56: Add the missing blank line before the “## Example Input” heading in
the agent.md content to satisfy the markdown spacing rule; update the markdown
around that example section so the list or preceding paragraph is separated from
the heading by a single empty line, keeping the “Example Input” heading as the
unique marker to locate the fix.
In `@kits/ai-startup-idea-validator/lamatic.config.ts`:
- Around line 29-32: The kit metadata in lamatic.config.ts still contains
placeholder link values, so update the links object in the config to use real
production URLs or remove the fields until they are available. Specifically, fix
the deploy and github entries in the links section so consumers do not see the
temporary PR link or an empty deploy target.
In `@kits/ai-startup-idea-validator/README.md`:
- Line 108: The README.md entry for the AgentKit list item is missing a trailing
newline at EOF, causing markdownlint MD047. Update the end of the document so
the final line terminates with a newline, keeping the existing content
unchanged.
- Around line 63-68: The setup section in README should point users to the
runnable app under apps instead of running commands from the kit root. Update
the install/run instructions in the README to navigate into apps before invoking
npm install and npm run dev, using the same setup block that documents the kit
workflow. Also ensure the README ends with a trailing newline.
---
Outside diff comments:
In `@kits/ai-startup-idea-validator/flows/ai-startup-idea-validator.ts`:
- Around line 4-16: The flow metadata in meta is still using template defaults,
so populate the missing fields instead of leaving them blank. Update the AI
Startup Idea Validator meta export to provide meaningful values for description,
tags, githubUrl, documentationUrl, deployUrl, and author.email, keeping the
existing meta object structure intact so the flow is published with complete
information.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: ASSERTIVE
Plan: Pro
Run ID: 182758a2-5bc9-43e1-ad75-24d090cd9baf
📒 Files selected for processing (6)
kits/ai-startup-idea-validator/README.mdkits/ai-startup-idea-validator/agent.mdkits/ai-startup-idea-validator/flows/ai-startup-idea-validator.tskits/ai-startup-idea-validator/lamatic.config.tskits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_system_0.mdkits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_user_1.md
Contributor
✅ Action performedReview finished.
|
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (5)
kits/ai-startup-idea-validator/lamatic.config.ts (1)
29-32: 📐 Maintainability & Code Quality | 🟡 MinorMission: swap out the placeholder links.
deployis empty andgithubstill points at the PR, so metadata consumers will keep showing temporary values. Replace them with real URLs or drop the fields until they exist.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@kits/ai-startup-idea-validator/lamatic.config.ts` around lines 29 - 32, The links metadata in the config still contains placeholder values, so update the links object in lamatic.config.ts to use real deploy and github URLs, or remove those fields entirely if they are not available yet. Locate the links block in the config and replace the empty deploy entry and PR-based github entry so metadata consumers no longer expose temporary values.kits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_user_1.md (1)
1-4: 📐 Maintainability & Code Quality | 🟡 MinorMission: close the file with a newline.
markdownlint still flags MD047 here.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@kits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_user_1.md` around lines 1 - 4, The startup idea prompt file is missing a trailing newline, which is causing markdownlint MD047. Update the markdown content generated in this prompt template so the file ends with a newline after the final line, preserving the existing text in the startup idea input block.Source: Linters/SAST tools
kits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_system_0.md (1)
34-35: 📐 Maintainability & Code Quality | 🟡 MinorMission: close the file with a newline.
markdownlint still flags MD047 here.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@kits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_system_0.md` around lines 34 - 35, The markdown prompt content is still triggering MD047 because the file is not ending with a newline; update the content in the system prompt markdown so it is terminated with a trailing newline while keeping the existing headings and bullet formatting intact. Use the markdown block in ai-startup-idea-validator_llmnode-585_system_0.md as the target and ensure the final character written to the file is a newline.Source: Linters/SAST tools
kits/ai-startup-idea-validator/README.md (1)
21-49: 📐 Maintainability & Code Quality | 🟡 MinorMission: point the setup steps at
apps/.As per coding guidelines, this README should guide users through the runnable app.
npm install/npm run devstill target the kit root even though the only manifest lives underapps/; addcd appsbefore both commands and keep the trailing newline at EOF.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@kits/ai-startup-idea-validator/README.md` around lines 21 - 49, The setup instructions in the README point at the wrong directory for running the app. Update the steps around the install and dev commands so they explicitly switch into the apps directory before running npm install and npm run dev, and ensure the README ends with a trailing newline. Keep the rest of the setup flow and the Architecture/Environment Variables sections unchanged.Source: Coding guidelines
kits/ai-startup-idea-validator/agent.md (1)
47-49: 📐 Maintainability & Code Quality | 🟡 MinorMission: close the file with a newline.
markdownlint still flags MD047 here.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@kits/ai-startup-idea-validator/agent.md` around lines 47 - 49, The agent.md file is missing a trailing newline, which is causing markdownlint MD047 to fail. Update the end of the document so the final line under the Environment Variables section is properly terminated with a newline, keeping the content unchanged and ensuring the file ends cleanly.Source: Linters/SAST tools
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@kits/ai-startup-idea-validator/apps/.env.example`:
- Around line 1-5: The .env.example content is wrapped in a fenced Markdown
block, which breaks plain dotenv usage. Update the example so it stays as raw
dotenv text by keeping the comment/header and the GEMINI_API_KEY assignment but
removing the opening and closing backticks; locate the example entry in the
.env.example file and ensure it is valid for dotenv tooling.
In `@kits/ai-startup-idea-validator/README.md`:
- Around line 23-35: The setup list in the README still triggers MD029 because
it uses sequential numbering; update the numbered steps so each item uses the
same repeated marker instead of incrementing numbers. Make this change in the
setup instructions list around the clone/import/configure/install/start steps,
keeping the existing content but normalizing the list formatting.
---
Duplicate comments:
In `@kits/ai-startup-idea-validator/agent.md`:
- Around line 47-49: The agent.md file is missing a trailing newline, which is
causing markdownlint MD047 to fail. Update the end of the document so the final
line under the Environment Variables section is properly terminated with a
newline, keeping the content unchanged and ensuring the file ends cleanly.
In `@kits/ai-startup-idea-validator/lamatic.config.ts`:
- Around line 29-32: The links metadata in the config still contains placeholder
values, so update the links object in lamatic.config.ts to use real deploy and
github URLs, or remove those fields entirely if they are not available yet.
Locate the links block in the config and replace the empty deploy entry and
PR-based github entry so metadata consumers no longer expose temporary values.
In
`@kits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_system_0.md`:
- Around line 34-35: The markdown prompt content is still triggering MD047
because the file is not ending with a newline; update the content in the system
prompt markdown so it is terminated with a trailing newline while keeping the
existing headings and bullet formatting intact. Use the markdown block in
ai-startup-idea-validator_llmnode-585_system_0.md as the target and ensure the
final character written to the file is a newline.
In
`@kits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_user_1.md`:
- Around line 1-4: The startup idea prompt file is missing a trailing newline,
which is causing markdownlint MD047. Update the markdown content generated in
this prompt template so the file ends with a newline after the final line,
preserving the existing text in the startup idea input block.
In `@kits/ai-startup-idea-validator/README.md`:
- Around line 21-49: The setup instructions in the README point at the wrong
directory for running the app. Update the steps around the install and dev
commands so they explicitly switch into the apps directory before running npm
install and npm run dev, and ensure the README ends with a trailing newline.
Keep the rest of the setup flow and the Architecture/Environment Variables
sections unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: ASSERTIVE
Plan: Pro
Run ID: 8af6a014-2f26-414a-be8f-b7948f64b13d
📒 Files selected for processing (7)
kits/ai-startup-idea-validator/README.mdkits/ai-startup-idea-validator/agent.mdkits/ai-startup-idea-validator/apps/.env.examplekits/ai-startup-idea-validator/flows/ai-startup-idea-validator.tskits/ai-startup-idea-validator/lamatic.config.tskits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_system_0.mdkits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_user_1.md
Comment on lines
+1
to
+5
| ## Environment Variables | ||
|
|
||
| ```env | ||
| GEMINI_API_KEY=your_gemini_api_key | ||
| ``` No newline at end of file |
Contributor
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Mission: keep this file as plain dotenv.
The fenced Markdown block makes the example invalid for dotenv tooling; keep the comment line and the key/value pair, but drop the backticks.
Suggested fix
## Environment Variables
-
-```env
GEMINI_API_KEY=your_gemini_api_key
-```📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ## Environment Variables | |
| ```env | |
| GEMINI_API_KEY=your_gemini_api_key | |
| ``` | |
| ## Environment Variables | |
| GEMINI_API_KEY=your_gemini_api_key |
🧰 Tools
🪛 dotenv-linter (4.0.0)
[warning] 3-3: [KeyWithoutValue] The ```env key should be with a value or have an equal sign
(KeyWithoutValue)
[warning] 3-3: [LeadingCharacter] Invalid leading character detected
(LeadingCharacter)
[warning] 3-3: [LowercaseKey] The ```env key should be in uppercase
(LowercaseKey)
[warning] 4-4: [UnorderedKey] The GEMINI_API_KEY key should go before the ```env key
(UnorderedKey)
[warning] 5-5: [EndingBlankLine] No blank line at the end of the file
(EndingBlankLine)
[warning] 5-5: [KeyWithoutValue] The ``` key should be with a value or have an equal sign
(KeyWithoutValue)
[warning] 5-5: [LeadingCharacter] Invalid leading character detected
(LeadingCharacter)
[warning] 5-5: [UnorderedKey] The key should go before theenv key
(UnorderedKey)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@kits/ai-startup-idea-validator/apps/.env.example` around lines 1 - 5, The
.env.example content is wrapped in a fenced Markdown block, which breaks plain
dotenv usage. Update the example so it stays as raw dotenv text by keeping the
comment/header and the GEMINI_API_KEY assignment but removing the opening and
closing backticks; locate the example entry in the .env.example file and ensure
it is valid for dotenv tooling.
Source: Linters/SAST tools
Comment on lines
+23
to
+35
| 1. Clone the repository. | ||
| 2. Import the flow into Lamatic Studio. | ||
| 3. Configure the required environment variables. | ||
| 4. Install dependencies: | ||
|
|
||
| ```bash | ||
| npm install | ||
| ``` | ||
|
|
||
| 5. Start the application: | ||
|
|
||
| ```bash | ||
| npm run dev |
Contributor
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Mission: normalize the setup list numbering.
markdownlint still reports MD029 on this list; switch the steps to repeated 1. markers.
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 32-32: Ordered list item prefix
Expected: 1; Actual: 5; Style: 1/1/1
(MD029, ol-prefix)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@kits/ai-startup-idea-validator/README.md` around lines 23 - 35, The setup
list in the README still triggers MD029 because it uses sequential numbering;
update the numbered steps so each item uses the same repeated marker instead of
incrementing numbers. Make this change in the setup instructions list around the
clone/import/configure/install/start steps, keeping the existing content but
normalizing the list formatting.
Source: Linters/SAST tools
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Checklist
1. Select Contribution Type
kits/<category>/<kit-name>/)bundles/<bundle-name>/)templates/<template-name>/)2. General Requirements
kebab-caseand matches the flow IDREADME.md(purpose, setup, usage)3. File Structure (Check what applies)
config.jsonpresent with valid metadata (name, description, tags, steps, author, env keys)flows/<flow-name>/(where applicable) include:config.json(Lamatic flow export)inputs.jsonmeta.jsonREADME.md.env.examplewith placeholder values only (kits only)config.jsonnode graphs (changes via Lamatic Studio export)4. Validation
npm install && npm run devworks locally (kits: UI runs; bundles/templates: flows are valid)[kit] Add <name> for <use case>)Added new kit
kits/ai-startup-idea-validator:kits/ai-startup-idea-validator/.gitignore(ignore.lamatic/,node_modules/,.env,.env.local)kits/ai-startup-idea-validator/README.md(kit overview, features, setup/run instructions, andGEMINI_API_KEYrequirement)kits/ai-startup-idea-validator/agent.md(agent identity, workflow, guardrails, integration/env var notes)kits/ai-startup-idea-validator/constitutions/default.md(default safety/data-handling/tone rules: harmful/illegal refusals, anti-jailbreak guidance, PII/logging constraints)kits/ai-startup-idea-validator/lamatic.config.ts(kit configuration + mandatory step wired to flow id viaAI_STARTUP_IDEA_VALIDATOR_FLOW_ID)kits/ai-startup-idea-validator/flows/ai-startup-idea-validator.ts(Lamatic flow definition + nodes/edges)kits/ai-startup-idea-validator/model-configs/ai-startup-idea-validator_llmnode-585_generative-model-name.ts(Gemini model/provider/credential mapping forllmnode-585)kits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_system_0.md(system prompt specifying required report sections + output formatting and viability scoring expectations)kits/ai-startup-idea-validator/prompts/ai-startup-idea-validator_llmnode-585_user_1.md(user prompt injecting the chat idea from the trigger node output)kits/ai-startup-idea-validator/apps/package.json(app scaffold with a placeholderdevscript)kits/ai-startup-idea-validator/apps/.env.example(placeholder-only env template containingGEMINI_API_KEY)Flow implementation details (
kits/ai-startup-idea-validator/flows/ai-startup-idea-validator.ts); noflow.jsonartifact present in the repo search:triggerNode(triggerNode_1, “Chat Widget” popup chat trigger)dynamicNode(LLMNode_585, “Generate Text” LLM node using system+user prompt templates and the configured generative model)responseNode(responseNode_triggerNode_1, returns generated text to the chat UI)triggerNode_1→LLMNode_585viadefaultEdgeLLMNode_585→responseNode_triggerNode_1viadefaultEdgetriggerNode_1→responseNode_triggerNode_1viaresponseEdgeresponseNode_triggerNode_1content:{{LLMNode_585.output.generatedResponse}}