portfolio-sync

Sync portfolio positions from Polymarket, Kalshi, and Manifold

Quality

59%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/portfolio-sync/SKILL.md

Quality

Discovery

54%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description effectively identifies a specific niche (prediction market portfolio syncing) with excellent platform-specific trigger terms. However, it lacks explicit 'when to use' guidance and could benefit from listing additional concrete actions beyond just syncing positions.

Suggestions

Add a 'Use when...' clause with trigger terms like 'prediction markets', 'betting positions', 'market portfolio', or when users mention any of the three platforms

Expand the action list to include related capabilities such as 'view balances', 'track P&L', 'compare positions across platforms', or 'export holdings'

Dimension	Reasoning	Score
Specificity	Names the domain (prediction market portfolios) and one action (sync positions), but doesn't list multiple concrete actions like viewing, analyzing, exporting, or comparing positions.	2 / 3
Completeness	Describes what it does (sync positions) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes excellent natural keywords users would say: 'portfolio', 'positions', and the three specific platform names (Polymarket, Kalshi, Manifold) that users would naturally mention when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Very clear niche with distinct platform names (Polymarket, Kalshi, Manifold) that are unlikely to conflict with other skills; prediction market portfolio syncing is a specific domain.	3 / 3
	Total	9 / 12 Passed

Implementation

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides comprehensive, executable code for syncing portfolio positions across three prediction market platforms. Its main strengths are actionability and concrete implementations. However, it's verbose for a skill file, lacks error handling/validation workflows, and would benefit from better progressive disclosure by splitting platform-specific code into separate reference files.

Suggestions

Add explicit error handling and validation steps (e.g., 'If API returns 401, re-authenticate; if rate limited, wait and retry') to improve workflow clarity

Split platform-specific implementations into separate files (e.g., POLYMARKET.md, KALSHI.md, MANIFOLD.md) and keep SKILL.md as a concise overview with the unified sync function

Remove the introductory sentence and consolidate the Position dataclass definition to appear once at the top rather than implicitly requiring all prior functions

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with executable code, but includes some unnecessary verbosity like the introductory sentence and could consolidate redundant patterns (e.g., multiple similar position-fetching functions with overlapping structure).	2 / 3
Actionability	Provides fully executable Python code for all three platforms with concrete API endpoints, data structures, and copy-paste ready examples including environment variable usage and complete function implementations.	3 / 3
Workflow Clarity	The skill presents individual platform sync methods and a unified sync function, but lacks explicit validation checkpoints or error handling guidance. No verification steps for confirming successful syncs or handling API failures.	2 / 3
Progressive Disclosure	Content is organized by platform with clear sections, but the skill is quite long (~300 lines) and could benefit from splitting platform-specific implementations into separate files with SKILL.md serving as an overview with references.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alsk1992/CloddsBot
Commit: 2a8c94e

Reviewed: 28 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.