Backend Analysis Skill
jiushiwon/wg-skills
后端项目静态分析技能。不运行项目，直接扫描源码，为 Java(Spring Boot/Spring Cloud)、Go(Gin/Echo)、Python(FastAPI/Django/Flask)、Node.js(Express/NestJS) 项目产出 4 份报告：① 接口报告（全部 API 清单：方法/路径/入参/出参/鉴权）② 技术报告（语言/框架版本、中间件如…
Investigate an existing non-Mendix application (Java, .NET, Python, Node, PHP, …) and produce a structured migration assessment for Mendix.
Install Assess Migration
$ npx skills add mendixlabs/mxcli --skill assess-migration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mendixlabs/mxcli assess-migration --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/mendix/assess-migration .claude/skills/assess-migration && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "assess-migration" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/assess-migration into .claude/skills/assess-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assess-migration", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/assess-migrationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mendixlabs/mxcli --skill assess-migration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mendixlabs/mxcli assess-migration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/mendix/assess-migration .agents/skills/assess-migration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "assess-migration" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/assess-migration into .agents/skills/assess-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assess-migration", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mendixlabs/mxcli --skill assess-migration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mendixlabs/mxcli assess-migration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/mendix/assess-migration .cursor/skills/assess-migration && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "assess-migration" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/assess-migration into .cursor/skills/assess-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assess-migration", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mendixlabs/mxcli.git --path .claude/skills/mendix/assess-migration--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mendixlabs/mxcli --skill assess-migration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mendixlabs/mxcli assess-migration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/mendix/assess-migration .gemini/skills/assess-migration && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "assess-migration" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/assess-migration into .gemini/skills/assess-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assess-migration", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mendixlabs/mxcli assess-migrationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mendixlabs/mxcli --skill assess-migration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/mendix/assess-migration .github/skills/assess-migration && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "assess-migration" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/assess-migration into .github/skills/assess-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assess-migration", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mendixlabs/mxcli --skill assess-migration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mendixlabs/mxcli assess-migration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/mendix/assess-migration .opencode/skills/assess-migration && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "assess-migration" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/assess-migration into .opencode/skills/assess-migration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assess-migration", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
assess-migration- GitHub stars
- 128
- Token cost
- ~3.6k tokens
- SKILL.md length
- 558 words
- Files
- 1
- Skills in repo
- 75
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Investigate an existing non-Mendix application (Java, .NET, Python, Node, PHP, …) and produce a structured migration assessment for Mendix.
- Works in 6 steps: Identify the Technology Stack → Map the Data Model → Catalog Business Logic and Rules → …
- Asked to analyse a legacy codebase for migration
- SKILL.md covers When to Use This Skill, Investigation Process, Assessment Report Template and Tips, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Assess Migration is an agent skill from mendixlabs/mxcli. Investigate an existing non-Mendix application (Java, .NET, Python, Node, PHP, …) and produce a structured migration assessment for Mendix. Use when asked to analyse a legacy codebase for migration, build a migration inventory, or size the effort before any MDL is written.
Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Backend development. It works with Java, .NET, PHP and Python. The repository describes itself as: Mendix cli tool, a headless way to work with Mendix projects. Enables Mendix projects for use with 3rd party agentic coding tools like Claude Code and Copilot. Includes a… The licence is Apache-2.0.
When your agent uses it
- Asked to analyse a legacy codebase for migration
- Build a migration inventory
- Size the effort before any MDL is written
Example prompts
- “/assess-migration”
Requirements
- Node.js
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a924d11. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Assess Migration loads about 3.6k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 558 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:24
ies`, `appsettings.json`, `web.config`, `.env`)
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mendixlabs/mxcli at commit a924d11, republished under its Apache-2.0 licence (© mendixlabs). 558 words, ~3,606 tokens.
Download SKILL.mdSave it as
.claude/skills/assess-migration/SKILL.md (or your agent's skills folder).- name
- assess-migration
- description
- Investigate an existing non-Mendix application (Java, .NET, Python, Node, PHP, …) and produce a structured migration assessment for Mendix. Use when asked to analyse a legacy codebase for migration, build a migration inventory, or size the effort before any MDL is written.
Migration Assessment: Investigating Non-Mendix Projects
This skill guides the investigation of existing non-Mendix applications to produce a structured migration assessment for Mendix.
When to Use This Skill
Use this skill when:
- A user asks to analyze an existing project for migration to Mendix
- Investigating a codebase in any technology (Java, .NET, Python, Node.js, PHP, etc.)
- Producing a migration inventory or assessment report
- Planning the scope and phases of a migration project
Investigation Process
Step 1: Identify the Technology Stack
Determine the application's technology stack by examining:
- Build files (
pom.xml,*.csproj,package.json,requirements.txt,Gemfile,composer.json) - Configuration files (
application.properties,appsettings.json,web.config,.env) - Framework indicators (Spring Boot, ASP.NET, Django, Express, Laravel, Rails)
- Database configuration (connection strings, ORM config, migration files)
- Frontend framework (
angular.json,next.config.js, Vue/React/Svelte indicators)
Step 2: Map the Data Model
Investigate and document all entities, their attributes, and relationships.
Where to look:
| Technology | Data Model Location |
|---|---|
| Java/Spring | @entity classes, JPA annotations, Hibernate mappings |
| .NET/EF | DbContext, entity classes, EF migrations |
| Django | models.py files |
| Rails | app/models/, db/schema.rb |
| Node.js | Sequelize/TypeORM/Prisma models, Mongoose schemas |
| PHP/Laravel | Eloquent models, migrations |
| Database-first | SQL schema, stored procedures, views |
Output format:
### data model
#### entities
| entity | attributes | type | Constraints | Mendix mapping |
|--------|-----------|------|-------------|----------------|
| Customer | id | long (auto) | PK | (auto-generated) |
| | name | string(200) | not null | string(200) |
| | email | string(200) | unique | string(200) |
| | creditLimit | decimal(10,2) | | decimal |
| | isActive | boolean | default true | boolean |
| | createdAt | datetime | | datetime |
| Order | id | long (auto) | PK | (auto-generated) |
| | orderNumber | string(50) | unique, not null | string(50) |
| | status | enum | | enumeration |
| | totalAmount | decimal | | decimal |
#### associations
| from | to | type | Mendix mapping |
|------|----|------|----------------|
| Order | Customer | Many-to-One | reference (Order → Customer) |
| Order | OrderLine | One-to-Many | reference (OrderLine → Order) |
| user | role | Many-to-Many | ReferenceSet |
#### enumerations
| Name | values | Used by |
|------|--------|---------|
| OrderStatus | PENDING, PROCESSING, COMPLETED, CANCELLED | Order.status |
| UserRole | ADMIN, MANAGER, user | User.role |Step 3: Catalog Business Logic and Rules
This is the most critical part. Identify and explicitly document all business logic, validation rules, calculations, and workflows.
Where to look:
| Technology | Logic Location |
|---|---|
| Java/Spring | @service classes, @Component, @Transactional methods |
| .NET | Service classes, domain logic, middleware |
| Django | Views, forms, signals, managers |
| Rails | Models (callbacks, validations), services, concerns |
| Node.js | Route handlers, middleware, service modules |
| Database | Stored procedures, triggers, functions, constraints |
Categorize each piece of logic:
### business Logic
#### validation rules
| rule | Location | description | Mendix mapping |
|------|----------|-------------|----------------|
| VR-001 | CustomerService.validate() | Customer name is required, max 200 chars | validation microflow |
| VR-002 | OrderService.validate() | Order date cannot be in the past | validation microflow |
| VR-003 | DB trigger: trg_check_credit | Credit limit cannot exceed $1M for non-premium | validation microflow + before commit |
| VR-004 | OrderLine model | Quantity must be > 0 | attribute validation |
#### business rules
| rule | Location | description | Mendix mapping |
|------|----------|-------------|----------------|
| BR-001 | OrderService.calculateTotal() | sum of line items * quantity, apply tax | microflow |
| BR-002 | DiscountService.applyDiscount() | 10% for orders > $1000, 15% for premium | microflow |
| BR-003 | CustomerService.updateStatus() | Deactivate customer after 12 months inactive | Scheduled microflow |
| BR-004 | DB proc: sp_close_month | Monthly closing with balance calculations | microflow + scheduled event |
#### workflows / multi-Step Processes
| workflow | Steps | description | Mendix mapping |
|----------|-------|-------------|----------------|
| Order Approval | Submit → Review → Approve/Reject → notify | Orders > $5000 need manager approval | workflow or microflow chain |
| user Onboarding | Register → Verify Email → Complete Profile → Activate | New user registration flow | microflow chain + pages |
#### calculated Fields / Derived data
| Field | Calculation | Location | Mendix mapping |
|-------|-------------|----------|----------------|
| Order.totalAmount | sum(lines.price * lines.qty) | OrderService | calculated attribute or microflow |
| Customer.orderCount | count(orders) | sql view | microflow or calculated attribute |
| Invoice.dueDate | invoiceDate + paymentTerms | InvoiceService | microflow |Step 4: Inventory Pages and UI
Document all screens, their purpose, and the data they display or edit.
Where to look:
| Technology | UI Location |
|---|---|
| Java/Spring MVC | JSP/Thymeleaf templates, controllers |
| .NET MVC/Razor | Views, Razor pages, controllers |
| React/Angular/Vue | Component files, route definitions |
| Django | Templates, URL conf |
| Rails | Views, routes |
| Mobile | Activities/Fragments (Android), ViewControllers (iOS) |
Output format:
### pages / Screens
| page | type | data | key actions | Mendix mapping |
|------|------|------|-------------|----------------|
| Customer list | overview | Customer (filtered, paged) | search, New, Edit, delete | overview page + datagrid |
| Customer Edit | Form | Customer + Addresses | Save, cancel, Validate | Edit page + dataview |
| Order Dashboard | Dashboard | Orders (grouped by status) | filter, Drill-down | page + multiple DataGrids |
| Order Entry | multi-step form | Order + OrderLines | add line, Calculate, Submit | page + listview + microflows |
| Reports | read-only | Aggregated data | export, Print | page + charts or custom widgets |
| login | authentication | Credentials | login, Forgot password | login page (built-in) |Step 5: Map Integrations
Document all external system connections, APIs consumed, and APIs exposed.
Where to look:
- REST/SOAP client configurations
- HTTP client usage, API base URLs
- Message queue consumers/producers (Kafka, RabbitMQ, SQS)
- File import/export (CSV, Excel, XML, JSON)
- Email sending configuration
- External authentication (OAuth, SAML, LDAP)
- Third-party SDK usage (payment, notification, storage)
Output format:
### Integrations
#### APIs consumed (Outbound)
| Integration | Protocol | Endpoint | auth | Mendix mapping |
|-------------|----------|----------|------|----------------|
| Payment Gateway | rest | api.stripe.com | api key | rest client (consumed) |
| Email service | rest | api.sendgrid.com | api key | Email module or rest |
| ERP Sync | SOAP | erp.company.com/ws | Certificate | Web service call |
| file storage | SDK | AWS S3 | IAM | FileDocument + custom java |
#### APIs exposed (Inbound)
| Endpoint | method | Purpose | Mendix mapping |
|----------|--------|---------|----------------|
| /api/customers | get, post | Customer CRUD | published rest service |
| /api/orders/{id} | get, put | Order management | published rest service |
| /webhooks/payment | post | Payment notifications | published rest service |
#### data Feeds
| Feed | format | Direction | Frequency | Mendix mapping |
|------|--------|-----------|-----------|----------------|
| Customer export | CSV | Outbound | Daily | Scheduled microflow + export mapping |
| Product catalog | xml | Inbound | Hourly | Scheduled microflow + import mapping |
| Financial data | odata | both | Real-time | external entities (odata) |
#### message Queues / events
| Queue/Topic | Direction | Purpose | Mendix mapping |
|-------------|-----------|---------|----------------|
| order-events | publish | Order status changes | business events |
| inventory-updates | subscribe | Stock level changes | business events |Show full SKILL.md (198 more words)Show less
Step 6: Document Security Model
Investigate how authentication, authorization, user roles, and data access control are implemented.
Where to look:
| Technology | Security Location |
|---|---|
| Java/Spring | Spring Security config, @PreAuthorize, @Secured, @RolesAllowed |
| .NET | [Authorize], Identity config, policies, claims |
| Django | @login_required, permissions, groups |
| Rails | Devise, CanCanCan/Pundit policies |
| Node.js | Passport.js, JWT middleware, RBAC libraries |
| Database | GRANT statements, row-level security |
Output format:
### security
#### authentication
| method | Details | Mendix mapping |
|--------|---------|----------------|
| username/password | local DB with bcrypt | Built-in authentication |
| oauth 2.0 | Google, Microsoft SSO | OIDC SSO module |
| SAML | Corporate IdP | SAML module |
| api Keys | for service accounts | Custom implementation |
#### user roles
| role | description | Rough Privileges | Mendix mapping |
|------|-------------|------------------|----------------|
| Admin | full system access | all CRUD, user management, settings | Administrator role |
| Manager | Department-level access | Approve orders, view reports, manage team | Custom module role |
| user | Standard operations | create/edit own records, view assigned | Custom module role |
| Viewer | read-only access | view only, no modifications | Custom module role |
| api service | Machine-to-machine | Specific api endpoints only | Custom module role |
#### data access rules
| entity | role | create | read | write | delete | constraint |
|--------|------|--------|------|-------|--------|------------|
| Customer | Admin | Yes | all | all | Yes | none |
| Customer | Manager | Yes | Department | Department | No | Department = User.Department |
| Customer | user | No | Own | Own | No | CreatedBy = CurrentUser |
| Order | Manager | Yes | Department | Department | No | status != 'Closed' |
#### row-level security / data Filtering
| rule | description | Mendix mapping |
|------|-------------|----------------|
| Department isolation | users only see their department's data | XPath constraint on entity access |
| Record ownership | users only edit records they created | xpath: `[CreatedBy = '[%CurrentUser%]']` |
| status-based locking | Closed records are read-only | xpath on write: `[status != 'Closed']` |Assessment Report Template
Combine all findings into a structured report:
# Migration Assessment: [Application Name]
## Executive Summary
- **Application**: [Name and brief description]
- **Technology stack**: [languages, frameworks, databases]
- **Size**: [entities, services/controllers, pages, integrations]
- **Complexity**: [Low / Medium / High]
- **Recommended approach**: [Big bang / Phased / Strangler fig]
## Inventory Summary
| Category | count | Complexity | Notes |
|----------|-------|------------|-------|
| entities | X | | |
| associations | X | | |
| enumerations | X | | |
| business rules | X | | list the critical ones |
| validation rules | X | | |
| pages/Screens | X | | |
| Integrations | X | | list external systems |
| user roles | X | | |
| Scheduled jobs | X | | |
## data model
[from Step 2]
## business Logic and rules
[from Step 3 — this is the most important section]
## pages and UI
[from Step 4]
## Integrations
[from Step 5]
## security
[from Step 6]
## Migration Risks
| Risk | impact | Mitigation |
|------|--------|------------|
| Complex stored procedures | Logic may not map 1:1 to microflows | Review and simplify, consider java actions |
| Custom UI components | No direct Mendix equivalent | Evaluate pluggable widgets or custom widgets |
| Real-time integrations | Mendix has different async patterns | Consider business events or polling |
| row-level security complexity | Mendix xpath constraints have limits | Simplify access rules where possible |
## Recommended Migration Phases
1. **Domain model** — entities, associations, enumerations
2. **Core business logic** — validation rules, business rules, calculations
3. **pages** — overview pages, edit forms, dashboards
4. **Integrations** — rest clients, file handling, external systems
5. **security** — roles, access rules, authentication
6. **Testing & cutover** — data migration, parallel running, go-liveTips
- Be thorough with business logic: This is where migrations fail. A missing validation rule or calculation creates bugs that are hard to trace back to the source.
- Check the database: Stored procedures, triggers, views, and constraints often contain business logic that isn't visible in application code.
- Look for implicit rules: Framework conventions (e.g., Rails validations, Spring annotations) encode rules that are easy to miss.
- Document what you DON'T migrate: Some features may not need to be migrated (legacy reports, dead code, deprecated features). Call these out explicitly.
- Ask about undocumented behavior: Users often know about special cases and workarounds that aren't in the code.
Related Skills
- /migrate-oracle-forms - Oracle Forms-specific migration
- /generate-domain-model - Creating entities and associations in MDL
- /write-microflows - Implementing business logic in MDL
- /organize-project - Folder structure for the migrated project
© mendixlabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/mendix/assess-migration of mendixlabs/mxcli.
Open the folder on GitHubat commit a924d11
Compare with similar skills
Assess Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Assess Migration this skillmendixlabs/mxcli | 128 | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| Backend Analysis Skilljiushiwon/wg-skills | 110 | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Dt Obs ServicesDynatrace/dynatrace-for-ai | 161 | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Rds Sqlserveraws/agent-toolkit-for-aws | 2.8k | — | ~6.3k | Automated safety check: Pass | Apache-2.0 | |
| Deprecated API UpdaterArabelaTso/Skills-4-SE | 253 | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Fastapi Templatesjh941213/my-cc-harness | 126 | — | ~945 | Automated safety check: Pass | None |
Similar skills
Dt Obs Services
Dynatrace/dynatrace-for-ai
Service performance monitoring with RED metrics (Rate, Errors, Duration) and runtime-specific telemetry for Java, .NET, Node.js, Python, PHP, and Go.
- Official
Rds Sqlserver
aws/agent-toolkit-for-aws
Provides connectivity, authentication, and troubleshooting guidance for Amazon RDS for SQL Server.
Deprecated API Updater
ArabelaTso/Skills-4-SE
Identify and replace deprecated API usage in source code with modern alternatives.
Fastapi Templates
jh941213/my-cc-harness
Production-grade FastAPI project creation and setup guide. An agent skill from jh941213/my-cc-harness.
Tsh Implementing Backend
TheSoftwareHouse/copilot-collections
Backend service implementation patterns, standards, and procedures.
More from mendixlabs/mxcli
All 75 skills in this repoMendix Odata Pushdown
mendixlabs/mxcli
Push OData query options into the SQL of a Mendix resource served by a read microflow, so $filter, $orderby, $top, $skip, $count and the key lookup reach the database instead of being silently…
Mendix Vega Charts
mendixlabs/mxcli
Chart a Mendix app with Vega-Lite through a pluggable widget that takes the specification and the data as separate properties, so the model emits rows and never assembles a chart payload.
Agents
mendixlabs/mxcli
Author Mendix AI agent documents in MDL — Model, Knowledge Base, Consumed MCP Service and Agent, with variables, tools and multi-line prompts.
Mendix Bulk Oql Dml
mendixlabs/mxcli
Run set-based INSERT, UPDATE and DELETE against Mendix entities through OQL statements, which the runtime supports and Studio Pro cannot author.
Mock REST APIs
mendixlabs/mxcli
Stand up an HTTP endpoint you control instead of a live third-party API, and point the Mendix app at it — Prism from an OpenAPI contract, a constant swap, or a forward proxy.
REST Client
mendixlabs/mxcli
Call external REST APIs from Mendix — the three approaches (inline REST CALL, consumed REST client document, generated from OpenAPI) and how to choose.
Related
Categories
Questions about Assess Migration
What does Assess Migration do?
Investigate an existing non-Mendix application (Java, .NET, Python, Node, PHP, …) and produce a structured migration assessment for Mendix. Assess Migration is an agent skill from mendixlabs/mxcli.NET, Python, Node, PHP, …) and produce a structured migration assessment for Mendix.
When should I use Assess Migration?
Assess Migration fits situations like: asked to analyse a legacy codebase for migration; build a migration inventory; size the effort before any MDL is written.
How do I install Assess Migration in Claude Code?
Run `npx skills add mendixlabs/mxcli --skill assess-migration -a claude-code`. Or copy the skill folder (.claude/skills/mendix/assess-migration in mendixlabs/mxcli) into .claude/skills/assess-migration in your project. Claude Code loads it when a task matches its description.
How do I install Assess Migration in Codex?
Run `npx skills add mendixlabs/mxcli --skill assess-migration -a codex`. Or copy the skill folder (.claude/skills/mendix/assess-migration in mendixlabs/mxcli) into .agents/skills/assess-migration in your project. Codex loads it when a task matches its description.
Can I use Assess Migration in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mendixlabs/mxcli --skill assess-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/assess-migration, .gemini/skills/assess-migration, .github/skills/assess-migration and .opencode/skills/assess-migration in your project.
What does Assess Migration need to run?
SKILL.md names no scripts, command-line tools or credentials: Assess Migration is instructions for the agent only. Our summary lists: Node.js.
Does Assess Migration access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Assess Migration safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Assess Migration use?
Assess Migration is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Assess Migration use?
About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Assess Migration?
Skills that share tags, products or a category with Assess Migration: Backend Analysis Skill (jiushiwon/wg-skills, 110 stars), Dt Obs Services (Dynatrace/dynatrace-for-ai, 161 stars), Rds Sqlserver (aws/agent-toolkit-for-aws, 2.8k stars) and Deprecated API Updater (ArabelaTso/Skills-4-SE, 253 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Assess Migration?
mendixlabs (a GitHub organization) maintains it in mendixlabs/mxcli, which has 128 GitHub stars. The repository holds 75 skills in this directory. The repository was last updated on October 7, 2026.
Source: mendixlabs/mxcli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.