migrate-application-operation

Create or migrate a protected Sim resource operation in the shared Principal and application-use-case architecture across internal APIs, public or versioned APIs, Copilot, and other trusted tool adapters. Use when adding a protected endpoint, tool command, or CRUD method; removing route- or tool-local authorization and business logic; consolidating resource reads or writes behind semantic operation policies; or adding another surface to an existing application operation while preserving contracts, identity, errors, rate limits, audit, analytics, and compatibility behavior. Treat v1, uploads, streams, large bodies, bulk recursion, and polymorphic tools as explicitly scoped special cases.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-5

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

A thorough, well-sequenced migration skill with strong validation checkpoints and concrete templates, though the TS examples are illustrative rather than copy-paste-ready. Its main weakness is progressive disclosure: everything lives in one large file with no reference bundle.

Suggestions

Split the per-surface adaptation sections (internal APIs, public/versioned APIs, Copilot, other tools) and the full test matrix into one-level-deep reference files (e.g. SURFACES.md, TESTING.md) linked from SKILL.md to improve progressive disclosure.

Tighten the repeated 'must not authorize/audit/query manually' invariant lists across surface sections into a single shared constraints block to reduce redundancy.

Where TS examples use placeholder domain names (widgetOperations, renameWidget), add a one-line note pointing to the golden-slice file (apps/sim/lib/workspace-files/...) that shows a real completed example, so the templates are easier to adapt correctly.

Dimension	Reasoning	Score
Conciseness	Dense, domain-specific rules that assume Claude's competence and avoid explaining known concepts, with only minor redundancy across surface sections; not a 5 because some invariant lists (the repeated 'must not authorize/audit manually' per surface) could be tightened.	4 / 5
Actionability	Provides concrete file paths to read, TS templates (defineWorkspaceOperation, defineAuthorizedWorkspaceUseCase, createCopilotApplicationAdapter) and executable bash checks (vitest, biome, turbo, check:api-validation:strict); not a 5 because the TS examples are intentionally illustrative templates with placeholder field names rather than copy-paste-ready code.	4 / 5
Workflow Clarity	Clear sequenced phases (read foundation, bound migration, freeze behavior, define operation, implement use case, adapt surfaces, test, hand off) with explicit fail-fast validation checkpoints, a full test matrix, and failure-sequencing guidance; the destructive/batch cap does not apply because validation is abundant.	5 / 5
Progressive Disclosure	Well-organized into section headers but monolithic at ~365 lines with no bundle files and no one-level-deep references; content such as per-surface adapter details and the large test matrix is inline and could be split into reference files. Not a 4 because there is no file-level disclosure at all, and not a 2 because in-file structure is genuinely clear.	3 / 5
	Total	16 / 20 Passed

Description

92%Weight 40%Scale 1-5

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

A strong, third-person description that explicitly states what the skill does and when to use it, with concrete actions and a distinct niche. It is slightly jargon-heavy, which keeps trigger-term quality just below the top anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Create or migrate a protected Sim resource operation', 'adding a protected endpoint, tool command, or CRUD method', 'removing route- or tool-local authorization and business logic', 'consolidating resource reads or writes', 'adding another surface' — with comprehensive coverage; not a 4 because the action set is broad and specific rather than having minor gaps.	5 / 5
Completeness	Explicitly answers both what ('Create or migrate a protected Sim resource operation...') and when ('Use when adding a protected endpoint, tool command, or CRUD method...') with concrete trigger phrases; clearly meets the top anchor.	5 / 5
Trigger Term Quality	Good keyword coverage with natural engineer-facing triggers ('protected endpoint', 'tool command', 'CRUD method', 'Copilot', 'semantic operation policies'); not a 5 because it leans on internal jargon ('Principal', 'application-use-case architecture') and lacks synonyms or file-extension variants a user might naturally say.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche tied to this codebase's 'Sim resource operation' / 'Principal and application-use-case architecture' with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: simstudioai/sim
Path: .agents/skills/migrate-application-operation/SKILL.md
Commit: 7945b29

Reviewed: 3 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.