Skip to content

Refresh the skill to include mcp usage#118

Merged
jackwildman merged 2 commits intomainfrom
update-skill
Feb 9, 2026
Merged

Refresh the skill to include mcp usage#118
jackwildman merged 2 commits intomainfrom
update-skill

Conversation

@jackwildman
Copy link
Copy Markdown
Contributor

No description provided.

@jackwildman jackwildman merged commit b22d625 into main Feb 9, 2026
4 checks passed
@jackwildman jackwildman deleted the update-skill branch February 9, 2026 17:42
Comment on lines 20 to +29

## Installation

### Python SDK

```bash
pip install everyrow
```

### MCP Server (for Claude Code, Claude Desktop, Cursor, etc.)
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The SKILL.md documentation for the everyrow_dedupe tool incorrectly lists a select_representative parameter, which is not implemented in the server, causing validation errors for users.
Severity: MEDIUM

Suggested Fix

Remove the select_representative parameter from the SKILL.md documentation for the everyrow_dedupe tool to match the actual implementation. To restore the intended functionality, consider exposing the strategy parameter from the underlying Python SDK in the DedupeInput model and updating the documentation accordingly.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: skills/everyrow-sdk/SKILL.md#L20-L29

Potential issue: The `SKILL.md` documentation for the `everyrow_dedupe` tool includes a
`select_representative` parameter. However, the server-side implementation in
`everyrow-mcp/src/everyrow_mcp/server.py` defines a `DedupeInput` model that does not
include this field. Because the model is configured with `extra="forbid"`, any attempt
to use the documented `select_representative` parameter will result in a validation
error, causing the tool to fail. This discrepancy misleads users and prevents them from
using the tool as documented. Additionally, the underlying SDK's `strategy` parameter is
not exposed, limiting functionality.

Did we get this right? 👍 / 👎 to inform future reviews.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant