Add Strale agent-capabilities cursor rule#212
Add Strale agent-capabilities cursor rule#212petterlindstrom79 wants to merge 3 commits intoPatrickJS:mainfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughAdds a new Changes
Sequence Diagram(s)sequenceDiagram
participant User as User/Agent
participant Agent as AI Agent
participant MCP as MCP Server
participant Strale as Strale Capability
participant Ext as External Data Source
User->>Agent: Request verification/compliance task
Agent->>MCP: strale_search(query) — locate capability slug
MCP-->>Agent: capability slug
Agent->>Strale: strale_execute(capability_slug, structured_input)
Strale->>Ext: optional fetch/extraction (web/PDF/invoice)
Ext-->>Strale: extracted structured data
Strale-->>Agent: structured JSON result + quality metadata
Agent->>User: return findings
Estimated code review effort🎯 2 (Simple) | ⏱️ ~5 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
![coderabbitai[bot]](https://avatars.gh.lumenfield.work/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
rules/strale-agent-capabilities-cursorrules-prompt-file/.cursorrules (1)
13-14: Verify the JSON configuration syntax.The JSON configuration on line 14 appears to be a single-line representation. While this is technically valid JSON, it may be harder for users to read and copy-paste correctly compared to a multi-line formatted example.
📝 Suggested formatting improvement for readability
-Setup (add to MCP config): -{ "mcpServers": { "strale": { "command": "npx", "args": ["-y", "strale-mcp"] } } } +Setup (add to MCP config): +```json +{ + "mcpServers": { + "strale": { + "command": "npx", + "args": ["-y", "strale-mcp"] + } + } +} +```🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@rules/strale-agent-capabilities-cursorrules-prompt-file/.cursorrules` around lines 13 - 14, The JSON example for the MCP config is valid but hard to read as a single line; reformat the single-line object into a readable multi-line JSON block so users can copy it easily—expand the top-level "mcpServers" object and the nested "strale" entry, placing "command": "npx" and "args": ["-y", "strale-mcp"] on their own lines (preserve keys "mcpServers", "strale", "command", and "args" and the argument "strale-mcp").
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@rules/strale-agent-capabilities-cursorrules-prompt-file/README.md`:
- Around line 1-4: Update the README to include author attribution: add an
"Author" line or short credits paragraph near the top of the file (e.g.,
directly under the title) that names the original author and optionally their
contact or source, and add a one-sentence note linking the README to the
corresponding .cursorrules file (e.g., "This README accompanies
rules/strale-agent-capabilities-cursorrules-prompt-file.cursorrules"). Ensure
the credit is clear and concise and matches the project’s author-attribution
style used elsewhere.
---
Nitpick comments:
In `@rules/strale-agent-capabilities-cursorrules-prompt-file/.cursorrules`:
- Around line 13-14: The JSON example for the MCP config is valid but hard to
read as a single line; reformat the single-line object into a readable
multi-line JSON block so users can copy it easily—expand the top-level
"mcpServers" object and the nested "strale" entry, placing "command": "npx" and
"args": ["-y", "strale-mcp"] on their own lines (preserve keys "mcpServers",
"strale", "command", and "args" and the argument "strale-mcp").
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 70134732-0c69-4de7-b06a-4a163b6a6de8
📒 Files selected for processing (2)
rules/strale-agent-capabilities-cursorrules-prompt-file/.cursorrulesrules/strale-agent-capabilities-cursorrules-prompt-file/README.md
|
Hi — just checking in on this PR. Happy to address any feedback or make adjustments if needed. Let me know if there's anything blocking the merge. |
|
Friendly ping — this has been open for a while. Let me know if there's anything I can do to move it forward. |
|
Hey — just a gentle nudge on this one. PR is still mergeable and CodeRabbit comments are addressed. Happy to rebase or adjust anything needed. Thanks! |
Drop "quality scores" and "250+ capabilities" claims; describe what the rule actually covers (company registry lookups, sanctions/PEP screening, financial validation, document extraction).
petterlindstrom79
changed the title
1 participant
Adds a
.cursorrulesrule for AI agents using Strale's data capabilities.Strale's MCP server (and SDK) gives agents access to a catalog of data capabilities — company registry lookups across 27 countries, sanctions/PEP screening, IBAN/VAT/LEI validation, web extraction, document parsing, and EU compliance checks. The rule tells the IDE-paired model when to reach for Strale and how to wire it up via MCP.
strale-mcp(MCP server, stdio + Streamable HTTP)straleio(npm + PyPI)Two files added:
.cursorrules(the rule) andREADME.md(companion doc). 71 lines total.Summary by CodeRabbit