[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-apache-manage-rest-api":3,"mdc--7chii9-key":43,"related-repo-apache-manage-rest-api":539,"related-org-apache-manage-rest-api":547},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":19,"repoUrl":20,"updatedAt":21,"license":22,"forks":23,"topics":24,"repo":38,"sourceUrl":41,"mdContent":42},"manage-rest-api","design and verify OFBiz REST APIs","Design, expose, refactor, and verify OFBiz REST APIs using the framework REST support, service engine contracts, native OFBiz services, and contract-safe wrapper patterns. Use when working with `.rest.xml` files, REST-exposed services, PWA\u002FAPI consumers, service export settings, or backend REST response contracts.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"apache","Apache Software Foundation","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fapache.png",[12,16],{"name":13,"slug":14,"type":15},"REST API","rest-api","tag",{"name":17,"slug":18,"type":15},"API Development","api-development",174,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fofbiz-plugins","2026-07-12T08:31:25.110226",null,214,[25,26,27,28,29,30,31,32,33,34,35,36,37],"content","database","geospatial","groovy","hacktoberfest","https","java","javascript","network-server","ofbiz","plugins","web-framework","xml",{"repoUrl":20,"stars":19,"forks":23,"topics":39,"description":40},[25,26,27,28,29,30,31,32,33,34,35,36,37],"Apache OFBiz is an open source product for the automation of enterprise processes. It includes framework components and business applications for ERP, CRM, E-Business\u002FE-Commerce, Supply Chain Management and Manufacturing Resource Planning. OFBiz provides a foundation and starting point for reliable, secure and scalable enterprise solutions.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fofbiz-plugins\u002Ftree\u002FHEAD\u002Fai-agent-skills\u002Fmanage-rest-api","---\nname: manage-rest-api\ndescription: Design, expose, refactor, and verify OFBiz REST APIs using the framework REST support, service engine contracts, native OFBiz services, and contract-safe wrapper patterns. Use when working with `.rest.xml` files, REST-exposed services, PWA\u002FAPI consumers, service export settings, or backend REST response contracts.\n---\n\n# Skill: Manage REST APIs\n\n## Goal\nBuild OFBiz REST APIs that are thin, service-native, contract-safe, and easy to upstream into OFBiz.\n\nUse OFBiz services, service definitions, entity utilities, and framework REST conventions first. Add REST wrapper services only when they adapt a transport contract, aggregate read data, or preserve compatibility for an existing consumer.\n\nFor low-level REST XML syntax, direct service export mechanics, SOAP integration, or controller JSON response patterns, also read the `manage-api-integration` skill.\n\n## Core Workflow\n1. **Map the contract first**\n   - Find the REST mapping, service definition, service implementation, and active consumers.\n   - Search frontend\u002FAPI clients before removing request parameters or response fields.\n   - Identify whether the endpoint is a generic service API, a read aggregate, or a compatibility adapter.\n\n2. **Prefer native OFBiz services**\n   - Reuse existing services before creating wrapper services.\n   - Expose native services directly when their inputs and outputs are already suitable for the REST contract.\n   - Keep write wrappers thin: resolve REST convenience parameters, delegate to native services, return the agreed response shape.\n\n3. **Let the service engine validate and coerce**\n   - Define service attributes with precise native types such as `Timestamp`, `BigDecimal`, `Double`, `Long`, and `Integer`.\n   - Avoid manual parsing in Groovy\u002FJava when service XML already declares the correct type.\n   - Use OFBiz conversion utilities only when conversion is genuinely needed inside service logic.\n\n4. **Use native query and paging utilities**\n   - Prefer `EntityQuery`, `filterByDate`, `queryCount`, and helper methods that already exist in the target codebase over custom query loops.\n   - Avoid N+1 queries by batch-loading related data and mapping in memory.\n   - Use database-level filtering\u002Fcounting where possible instead of loading full rows and filtering manually.\n\n5. **Promote shared mechanics carefully**\n   - Reuse existing OFBiz\u002Fframework\u002Fcomponent utilities before adding local helpers.\n   - Promote repeated mechanical patterns to the narrowest appropriate shared utility.\n   - Do not promote domain-specific behavior into generic utilities just because the method is small.\n\n6. **Verify with project-standard checks**\n   - Run the repository's standard backend compilation, static analysis, and relevant tests.\n   - Use the runtime\u002FJDK version required by the project build configuration.\n   - If a full check is blocked by environment or unrelated project issues, run the narrowest equivalent verification and report that it was targeted.\n\n## Helper Availability\n- Before using a helper for paging, partial-list slicing, case-insensitive parameter lookup, composite REST ID handling, or REST error shaping, confirm that the helper already exists in the target codebase or is being introduced in the same change.\n- If a helper is not available yet, prefer native `EntityQuery`, service engine typing\u002Fvalidation, and small local endpoint logic over adding a dependency on a missing framework API.\n\n## Wrapper Decision Rules\nCreate or keep a wrapper when it:\n- Aggregates multiple native service\u002Fentity reads for a REST\u002FPWA screen.\n- Preserves a published REST contract that differs from native OFBiz service shape.\n- Resolves REST-friendly identifiers into native key fields when the client cannot send native keys directly.\n- Adds read-side display metadata that avoids excessive client round trips.\n\nRemove or avoid a wrapper when it:\n- Only duplicates a native CRUD service call.\n- Manually validates what the service definition or native service already validates.\n- Re-parses typed service parameters.\n- Adds local formatting\u002Fconversion helpers already available in OFBiz.\n\nRead [service-wrapper-patterns.md](references\u002Fservice-wrapper-patterns.md) before adding or removing wrapper services.\n\n## Contract Safety\nBefore changing a REST response:\n- Search active consumers for every field you plan to remove.\n- Update frontend\u002Fclient mappers and tests in the same change when intentionally changing a contract.\n- Keep compatibility fields only when still used or intentionally supported.\n- Prefer stable semantic field names over implementation-detail names.\n\nRead [rest-contract-checklist.md](references\u002Frest-contract-checklist.md) before changing existing API inputs, paths, response fields, or service export settings.\n\n## REST Mapping Guidance\n- Keep REST XML mappings declarative and close to service names.\n- Prefer path parameters for stable resource identity and query parameters for filtering\u002Fpaging.\n- Use request bodies for create\u002Fupdate\u002Fremove payloads, especially when native OFBiz services require multiple key fields.\n- For multi-column keys, prefer native key fields in the body when that enables direct native service use. Use a stable composite REST identifier only when the REST contract truly needs one path\u002Fid value. Do not distort the underlying entity model.\n- Ensure services exposed through REST are intentionally exported and authorized.\n\n## Utility Promotion Test\nBefore adding a helper, answer:\n- Is this already available in OFBiz?\n- Is this repeated mechanical logic, or domain behavior?\n- Is the helper useful outside this one endpoint?\n- What is the narrowest appropriate owner: existing framework utility, component utility, or local script?\n\nGood utility candidates are mechanical patterns such as batch lookup, case-insensitive ID search, pagination wrappers, or composite ID creation, but only when those helpers already exist in the target codebase or are being introduced in the same change. Poor candidates are domain queries such as \"routing task associations\" or \"BOM component rows\"; keep those near the service that owns the domain meaning.\n",{"data":44,"body":45},{"name":4,"description":6},{"type":46,"children":47},"root",[48,57,64,70,75,89,95,318,324,344,350,355,378,383,406,420,426,431,454,466,472,500,506,511,534],{"type":49,"tag":50,"props":51,"children":53},"element","h1",{"id":52},"skill-manage-rest-apis",[54],{"type":55,"value":56},"text","Skill: Manage REST APIs",{"type":49,"tag":58,"props":59,"children":61},"h2",{"id":60},"goal",[62],{"type":55,"value":63},"Goal",{"type":49,"tag":65,"props":66,"children":67},"p",{},[68],{"type":55,"value":69},"Build OFBiz REST APIs that are thin, service-native, contract-safe, and easy to upstream into OFBiz.",{"type":49,"tag":65,"props":71,"children":72},{},[73],{"type":55,"value":74},"Use OFBiz services, service definitions, entity utilities, and framework REST conventions first. Add REST wrapper services only when they adapt a transport contract, aggregate read data, or preserve compatibility for an existing consumer.",{"type":49,"tag":65,"props":76,"children":77},{},[78,80,87],{"type":55,"value":79},"For low-level REST XML syntax, direct service export mechanics, SOAP integration, or controller JSON response patterns, also read the ",{"type":49,"tag":81,"props":82,"children":84},"code",{"className":83},[],[85],{"type":55,"value":86},"manage-api-integration",{"type":55,"value":88}," skill.",{"type":49,"tag":58,"props":90,"children":92},{"id":91},"core-workflow",[93],{"type":55,"value":94},"Core Workflow",{"type":49,"tag":96,"props":97,"children":98},"ol",{},[99,128,154,218,266,292],{"type":49,"tag":100,"props":101,"children":102},"li",{},[103,109],{"type":49,"tag":104,"props":105,"children":106},"strong",{},[107],{"type":55,"value":108},"Map the contract first",{"type":49,"tag":110,"props":111,"children":112},"ul",{},[113,118,123],{"type":49,"tag":100,"props":114,"children":115},{},[116],{"type":55,"value":117},"Find the REST mapping, service definition, service implementation, and active consumers.",{"type":49,"tag":100,"props":119,"children":120},{},[121],{"type":55,"value":122},"Search frontend\u002FAPI clients before removing request parameters or response fields.",{"type":49,"tag":100,"props":124,"children":125},{},[126],{"type":55,"value":127},"Identify whether the endpoint is a generic service API, a read aggregate, or a compatibility adapter.",{"type":49,"tag":100,"props":129,"children":130},{},[131,136],{"type":49,"tag":104,"props":132,"children":133},{},[134],{"type":55,"value":135},"Prefer native OFBiz services",{"type":49,"tag":110,"props":137,"children":138},{},[139,144,149],{"type":49,"tag":100,"props":140,"children":141},{},[142],{"type":55,"value":143},"Reuse existing services before creating wrapper services.",{"type":49,"tag":100,"props":145,"children":146},{},[147],{"type":55,"value":148},"Expose native services directly when their inputs and outputs are already suitable for the REST contract.",{"type":49,"tag":100,"props":150,"children":151},{},[152],{"type":55,"value":153},"Keep write wrappers thin: resolve REST convenience parameters, delegate to native services, return the agreed response shape.",{"type":49,"tag":100,"props":155,"children":156},{},[157,162],{"type":49,"tag":104,"props":158,"children":159},{},[160],{"type":55,"value":161},"Let the service engine validate and coerce",{"type":49,"tag":110,"props":163,"children":164},{},[165,208,213],{"type":49,"tag":100,"props":166,"children":167},{},[168,170,176,178,184,185,191,192,198,200,206],{"type":55,"value":169},"Define service attributes with precise native types such as ",{"type":49,"tag":81,"props":171,"children":173},{"className":172},[],[174],{"type":55,"value":175},"Timestamp",{"type":55,"value":177},", ",{"type":49,"tag":81,"props":179,"children":181},{"className":180},[],[182],{"type":55,"value":183},"BigDecimal",{"type":55,"value":177},{"type":49,"tag":81,"props":186,"children":188},{"className":187},[],[189],{"type":55,"value":190},"Double",{"type":55,"value":177},{"type":49,"tag":81,"props":193,"children":195},{"className":194},[],[196],{"type":55,"value":197},"Long",{"type":55,"value":199},", and ",{"type":49,"tag":81,"props":201,"children":203},{"className":202},[],[204],{"type":55,"value":205},"Integer",{"type":55,"value":207},".",{"type":49,"tag":100,"props":209,"children":210},{},[211],{"type":55,"value":212},"Avoid manual parsing in Groovy\u002FJava when service XML already declares the correct type.",{"type":49,"tag":100,"props":214,"children":215},{},[216],{"type":55,"value":217},"Use OFBiz conversion utilities only when conversion is genuinely needed inside service logic.",{"type":49,"tag":100,"props":219,"children":220},{},[221,226],{"type":49,"tag":104,"props":222,"children":223},{},[224],{"type":55,"value":225},"Use native query and paging utilities",{"type":49,"tag":110,"props":227,"children":228},{},[229,256,261],{"type":49,"tag":100,"props":230,"children":231},{},[232,234,240,241,247,248,254],{"type":55,"value":233},"Prefer ",{"type":49,"tag":81,"props":235,"children":237},{"className":236},[],[238],{"type":55,"value":239},"EntityQuery",{"type":55,"value":177},{"type":49,"tag":81,"props":242,"children":244},{"className":243},[],[245],{"type":55,"value":246},"filterByDate",{"type":55,"value":177},{"type":49,"tag":81,"props":249,"children":251},{"className":250},[],[252],{"type":55,"value":253},"queryCount",{"type":55,"value":255},", and helper methods that already exist in the target codebase over custom query loops.",{"type":49,"tag":100,"props":257,"children":258},{},[259],{"type":55,"value":260},"Avoid N+1 queries by batch-loading related data and mapping in memory.",{"type":49,"tag":100,"props":262,"children":263},{},[264],{"type":55,"value":265},"Use database-level filtering\u002Fcounting where possible instead of loading full rows and filtering manually.",{"type":49,"tag":100,"props":267,"children":268},{},[269,274],{"type":49,"tag":104,"props":270,"children":271},{},[272],{"type":55,"value":273},"Promote shared mechanics carefully",{"type":49,"tag":110,"props":275,"children":276},{},[277,282,287],{"type":49,"tag":100,"props":278,"children":279},{},[280],{"type":55,"value":281},"Reuse existing OFBiz\u002Fframework\u002Fcomponent utilities before adding local helpers.",{"type":49,"tag":100,"props":283,"children":284},{},[285],{"type":55,"value":286},"Promote repeated mechanical patterns to the narrowest appropriate shared utility.",{"type":49,"tag":100,"props":288,"children":289},{},[290],{"type":55,"value":291},"Do not promote domain-specific behavior into generic utilities just because the method is small.",{"type":49,"tag":100,"props":293,"children":294},{},[295,300],{"type":49,"tag":104,"props":296,"children":297},{},[298],{"type":55,"value":299},"Verify with project-standard checks",{"type":49,"tag":110,"props":301,"children":302},{},[303,308,313],{"type":49,"tag":100,"props":304,"children":305},{},[306],{"type":55,"value":307},"Run the repository's standard backend compilation, static analysis, and relevant tests.",{"type":49,"tag":100,"props":309,"children":310},{},[311],{"type":55,"value":312},"Use the runtime\u002FJDK version required by the project build configuration.",{"type":49,"tag":100,"props":314,"children":315},{},[316],{"type":55,"value":317},"If a full check is blocked by environment or unrelated project issues, run the narrowest equivalent verification and report that it was targeted.",{"type":49,"tag":58,"props":319,"children":321},{"id":320},"helper-availability",[322],{"type":55,"value":323},"Helper Availability",{"type":49,"tag":110,"props":325,"children":326},{},[327,332],{"type":49,"tag":100,"props":328,"children":329},{},[330],{"type":55,"value":331},"Before using a helper for paging, partial-list slicing, case-insensitive parameter lookup, composite REST ID handling, or REST error shaping, confirm that the helper already exists in the target codebase or is being introduced in the same change.",{"type":49,"tag":100,"props":333,"children":334},{},[335,337,342],{"type":55,"value":336},"If a helper is not available yet, prefer native ",{"type":49,"tag":81,"props":338,"children":340},{"className":339},[],[341],{"type":55,"value":239},{"type":55,"value":343},", service engine typing\u002Fvalidation, and small local endpoint logic over adding a dependency on a missing framework API.",{"type":49,"tag":58,"props":345,"children":347},{"id":346},"wrapper-decision-rules",[348],{"type":55,"value":349},"Wrapper Decision Rules",{"type":49,"tag":65,"props":351,"children":352},{},[353],{"type":55,"value":354},"Create or keep a wrapper when it:",{"type":49,"tag":110,"props":356,"children":357},{},[358,363,368,373],{"type":49,"tag":100,"props":359,"children":360},{},[361],{"type":55,"value":362},"Aggregates multiple native service\u002Fentity reads for a REST\u002FPWA screen.",{"type":49,"tag":100,"props":364,"children":365},{},[366],{"type":55,"value":367},"Preserves a published REST contract that differs from native OFBiz service shape.",{"type":49,"tag":100,"props":369,"children":370},{},[371],{"type":55,"value":372},"Resolves REST-friendly identifiers into native key fields when the client cannot send native keys directly.",{"type":49,"tag":100,"props":374,"children":375},{},[376],{"type":55,"value":377},"Adds read-side display metadata that avoids excessive client round trips.",{"type":49,"tag":65,"props":379,"children":380},{},[381],{"type":55,"value":382},"Remove or avoid a wrapper when it:",{"type":49,"tag":110,"props":384,"children":385},{},[386,391,396,401],{"type":49,"tag":100,"props":387,"children":388},{},[389],{"type":55,"value":390},"Only duplicates a native CRUD service call.",{"type":49,"tag":100,"props":392,"children":393},{},[394],{"type":55,"value":395},"Manually validates what the service definition or native service already validates.",{"type":49,"tag":100,"props":397,"children":398},{},[399],{"type":55,"value":400},"Re-parses typed service parameters.",{"type":49,"tag":100,"props":402,"children":403},{},[404],{"type":55,"value":405},"Adds local formatting\u002Fconversion helpers already available in OFBiz.",{"type":49,"tag":65,"props":407,"children":408},{},[409,411,418],{"type":55,"value":410},"Read ",{"type":49,"tag":412,"props":413,"children":415},"a",{"href":414},"references\u002Fservice-wrapper-patterns.md",[416],{"type":55,"value":417},"service-wrapper-patterns.md",{"type":55,"value":419}," before adding or removing wrapper services.",{"type":49,"tag":58,"props":421,"children":423},{"id":422},"contract-safety",[424],{"type":55,"value":425},"Contract Safety",{"type":49,"tag":65,"props":427,"children":428},{},[429],{"type":55,"value":430},"Before changing a REST response:",{"type":49,"tag":110,"props":432,"children":433},{},[434,439,444,449],{"type":49,"tag":100,"props":435,"children":436},{},[437],{"type":55,"value":438},"Search active consumers for every field you plan to remove.",{"type":49,"tag":100,"props":440,"children":441},{},[442],{"type":55,"value":443},"Update frontend\u002Fclient mappers and tests in the same change when intentionally changing a contract.",{"type":49,"tag":100,"props":445,"children":446},{},[447],{"type":55,"value":448},"Keep compatibility fields only when still used or intentionally supported.",{"type":49,"tag":100,"props":450,"children":451},{},[452],{"type":55,"value":453},"Prefer stable semantic field names over implementation-detail names.",{"type":49,"tag":65,"props":455,"children":456},{},[457,458,464],{"type":55,"value":410},{"type":49,"tag":412,"props":459,"children":461},{"href":460},"references\u002Frest-contract-checklist.md",[462],{"type":55,"value":463},"rest-contract-checklist.md",{"type":55,"value":465}," before changing existing API inputs, paths, response fields, or service export settings.",{"type":49,"tag":58,"props":467,"children":469},{"id":468},"rest-mapping-guidance",[470],{"type":55,"value":471},"REST Mapping Guidance",{"type":49,"tag":110,"props":473,"children":474},{},[475,480,485,490,495],{"type":49,"tag":100,"props":476,"children":477},{},[478],{"type":55,"value":479},"Keep REST XML mappings declarative and close to service names.",{"type":49,"tag":100,"props":481,"children":482},{},[483],{"type":55,"value":484},"Prefer path parameters for stable resource identity and query parameters for filtering\u002Fpaging.",{"type":49,"tag":100,"props":486,"children":487},{},[488],{"type":55,"value":489},"Use request bodies for create\u002Fupdate\u002Fremove payloads, especially when native OFBiz services require multiple key fields.",{"type":49,"tag":100,"props":491,"children":492},{},[493],{"type":55,"value":494},"For multi-column keys, prefer native key fields in the body when that enables direct native service use. Use a stable composite REST identifier only when the REST contract truly needs one path\u002Fid value. Do not distort the underlying entity model.",{"type":49,"tag":100,"props":496,"children":497},{},[498],{"type":55,"value":499},"Ensure services exposed through REST are intentionally exported and authorized.",{"type":49,"tag":58,"props":501,"children":503},{"id":502},"utility-promotion-test",[504],{"type":55,"value":505},"Utility Promotion Test",{"type":49,"tag":65,"props":507,"children":508},{},[509],{"type":55,"value":510},"Before adding a helper, answer:",{"type":49,"tag":110,"props":512,"children":513},{},[514,519,524,529],{"type":49,"tag":100,"props":515,"children":516},{},[517],{"type":55,"value":518},"Is this already available in OFBiz?",{"type":49,"tag":100,"props":520,"children":521},{},[522],{"type":55,"value":523},"Is this repeated mechanical logic, or domain behavior?",{"type":49,"tag":100,"props":525,"children":526},{},[527],{"type":55,"value":528},"Is the helper useful outside this one endpoint?",{"type":49,"tag":100,"props":530,"children":531},{},[532],{"type":55,"value":533},"What is the narrowest appropriate owner: existing framework utility, component utility, or local script?",{"type":49,"tag":65,"props":535,"children":536},{},[537],{"type":55,"value":538},"Good utility candidates are mechanical patterns such as batch lookup, case-insensitive ID search, pagination wrappers, or composite ID creation, but only when those helpers already exist in the target codebase or are being introduced in the same change. Poor candidates are domain queries such as \"routing task associations\" or \"BOM component rows\"; keep those near the service that owns the domain meaning.",{"items":540,"total":546},[541],{"slug":4,"name":4,"fn":5,"description":6,"org":542,"tags":543,"stars":19,"repoUrl":20,"updatedAt":21},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[544,545],{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},1,{"items":548,"total":701},[549,567,582,595,608,621,638,649,659,670,680,690],{"slug":550,"name":550,"fn":551,"description":552,"org":553,"tags":554,"stars":564,"repoUrl":565,"updatedAt":566},"datafusion-python","write Apache DataFusion Python code","Use when the user is writing datafusion-python (Apache DataFusion Python bindings) DataFrame or SQL code. Covers imports, data loading, DataFrame operations, expression building, SQL-to-DataFrame mappings, idiomatic patterns, and common pitfalls.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[555,558,561],{"name":556,"slug":557,"type":15},"Data Analysis","data-analysis",{"name":559,"slug":560,"type":15},"Python","python",{"name":562,"slug":563,"type":15},"SQL","sql",593,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fdatafusion-python","2026-07-12T08:36:04.957626",{"slug":568,"name":568,"fn":569,"description":570,"org":571,"tags":572,"stars":579,"repoUrl":580,"updatedAt":581},"bydbql","generate and execute BanyanDB BydbQL queries","Generate, validate, and optionally execute read-only BanyanDB BydbQL for STREAM, MEASURE, TRACE, and PROPERTY resources. Use when the user asks to query BanyanDB, translate natural language to BydbQL, inspect BanyanDB schema or data, validate BydbQL, or fetch raw BanyanDB records.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[573,576,578],{"name":574,"slug":575,"type":15},"Analytics","analytics",{"name":577,"slug":26,"type":15},"Database",{"name":562,"slug":563,"type":15},344,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fskywalking-banyandb","2026-07-12T08:31:01.294423",{"slug":583,"name":583,"fn":584,"description":585,"org":586,"tags":587,"stars":579,"repoUrl":580,"updatedAt":594},"compiling","compile and build BanyanDB projects","Compile and build the SkyWalking BanyanDB project. Use when the user asks to compile, build, or generate code for this project.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[588,591],{"name":589,"slug":590,"type":15},"Build","build",{"name":592,"slug":593,"type":15},"Engineering","engineering","2026-07-12T08:31:06.373309",{"slug":596,"name":596,"fn":597,"description":598,"org":599,"tags":600,"stars":579,"repoUrl":580,"updatedAt":607},"gh-pull-request","create GitHub pull requests for BanyanDB","Create a GitHub pull request for SkyWalking BanyanDB. Use when the user asks to create a PR, submit changes, or open a pull request.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[601,604],{"name":602,"slug":603,"type":15},"GitHub","github",{"name":605,"slug":606,"type":15},"Pull Requests","pull-requests","2026-07-12T08:31:03.792415",{"slug":609,"name":609,"fn":610,"description":611,"org":612,"tags":613,"stars":579,"repoUrl":580,"updatedAt":620},"vendor-update","update Go and Node.js vendor dependencies","Upgrade Go\u002FNode.js vendor dependencies and sync tool versions. Use whenever the user says \"upgrade dependencies\", \"update vendors\", \"vendor update\", \"run vendor-upgrade\", \"bump dependencies\", \"update packages\", or asks to run the `vendor-update` Make target. This skill also checks `scripts\u002Fbuild\u002Fversion.mk` after upgrading to see if any tracked tool versions need updating too, and removes stale binaries from `bin\u002F` when versions change.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[614,617],{"name":615,"slug":616,"type":15},"Go","go",{"name":618,"slug":619,"type":15},"Node.js","node-js","2026-07-12T08:31:02.555555",{"slug":622,"name":622,"fn":623,"description":624,"org":625,"tags":626,"stars":635,"repoUrl":636,"updatedAt":637},"cayenne-cgen","generate Cayenne entity Java classes","Use this skill whenever the user wants to (re)generate Cayenne entity Java classes from a DataMap. Trigger on phrases like 'generate Java classes', 'regenerate entities', 'run cgen', 'create the entity classes', 'why is the Artist class missing fields', 'where did the `_Abstract*` classes come from', 'sync the entity classes with the model', or any request to materialize Java from the DataMap. Also trigger as a follow-up after modeling changes (someone added an entity, attribute, or relationship and now the Java side is stale). This skill exclusively uses the `mcp__cayenne__cgen_run` MCP tool — it does NOT use `mvn cayenne:cgen` or the Gradle cgen task.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[627,630,632],{"name":628,"slug":629,"type":15},"Data Modeling","data-modeling",{"name":631,"slug":31,"type":15},"Java",{"name":633,"slug":634,"type":15},"ORM","orm",343,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fcayenne","2026-07-12T08:32:33.575211",{"slug":639,"name":639,"fn":640,"description":641,"org":642,"tags":643,"stars":635,"repoUrl":636,"updatedAt":648},"cayenne-db-import","import database schema into Cayenne DataMaps","Use this skill when the user wants to import database schema metadata into a Cayenne DataMap — the *model\u002Fmapping only*, not names or Java classes. Trigger on phrases like 'reverse engineer the database', 'import the schema', 'generate a DataMap from my DB', 'add the new tables from the DB into the model', 'import the customer table', 'create entities from these tables', or any request to read database metadata to populate or update a DataMap's XML. This is for *full schema* or *bulk table* import; one-off a-la-carte entity additions belong in the cayenne-modeling skill. IMPORTANT — scope: this imports the mapping ONLY; it does not clean up the Object-layer names or (re)generate Java classes. When the user wants their whole project brought in line with the DB ('sync my project with the database', 'my schema changed, update everything', 'update my entities\u002Fclasses from the DB'), that is the end-to-end `cayenne-full-db-sync` skill, which runs this import and then name cleanup and class generation. To regenerate classes alone use `cayenne-cgen`. The skill runs reverse engineering directly via the `mcp__cayenne__dbimport_run` MCP tool when a DBConnector is already configured; otherwise it opens the CayenneModeler GUI via `mcp__cayenne__open_project` to configure the connection first.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[644,645,646,647],{"name":577,"slug":26,"type":15},{"name":631,"slug":31,"type":15},{"name":633,"slug":634,"type":15},{"name":562,"slug":563,"type":15},"2026-07-19T05:40:33.655062",{"slug":650,"name":650,"fn":651,"description":652,"org":653,"tags":654,"stars":635,"repoUrl":636,"updatedAt":658},"cayenne-full-db-sync","synchronize Cayenne projects with database","Use this skill when the user wants to bring their WHOLE Cayenne project in line with the database in one shot — the mapping, the Object-layer names, and the generated Java classes together. This is the end-to-end 'sync with the DB' workflow, and it orchestrates three skills in order: `cayenne-db-import` (import schema metadata into the DataMap) → `cayenne-model-naming` (polish the just-imported names) → `cayenne-cgen` (regenerate Java classes). Trigger on holistic phrases like 'sync my project with the database', 'sync with the DB', 'my schema changed, update everything', 'update my entities\u002Fclasses from the database', 'reverse engineer and regenerate the classes', 'import the new tables and rebuild the entities', 'full DB sync', 'bring the model and classes up to date with the DB'. The distinguishing signal is scope: the user wants the whole project (mapping + names + Java code), not just one stage. For the *model\u002Fmapping only* (no name cleanup, no class generation) use `cayenne-db-import`; to (re)generate classes alone use `cayenne-cgen`; to clean names alone use `cayenne-model-naming`. Uses the `mcp__cayenne__dbimport_run` and `mcp__cayenne__cgen_run` MCP tools via the sub-skills; does NOT use Maven or Gradle goals.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[655,656,657],{"name":577,"slug":26,"type":15},{"name":631,"slug":31,"type":15},{"name":633,"slug":634,"type":15},"2026-07-19T06:03:49.112969",{"slug":660,"name":660,"fn":661,"description":662,"org":663,"tags":664,"stars":635,"repoUrl":636,"updatedAt":669},"cayenne-model-naming","clean up Cayenne object-layer names","Use this skill to clean up Object-layer names in a Cayenne DataMap — ObjEntity, ObjAttribute, and ObjRelationship names, plus DbRelationship names (the first-class unit of relationship cleanup — every FK has one whether or not an ObjRelationship was generated; the ObjRelationship name is synced to it when one exists) — so they read as descriptive, consistent Java. Trigger on phrases like 'clean up the model names', 'fix the entity names', 'these names look ugly', 'make the names descriptive', 'normalize the ObjEntity\u002Fattribute\u002Frelationship names', 'why is this relationship called team1', 'rename entities to be consistent', 'the import produced Gametype instead of GameType'. Invoke it on an explicit user request, or as a manual follow-up after a `cayenne-db-import` to polish the just-imported additions — it is never triggered automatically. IMPORTANT: this is a LIGHT polish pass — CayenneModeler's reverse-engineering already produces good names for the common case; only improve the specific things its deterministic algorithm cannot (run-together names with no separators like `gametype`, meaningless numbered names like `team1` from multiple relationships between two tables, and a common entity prefix that leaks into relationship names like `aaOrders`). Do NOT rewrite names that are already correct. This is Obj-layer naming polish; for structural model edits use `cayenne-modeling`, and for regenerating classes afterward use `cayenne-cgen`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[665,666,667,668],{"name":628,"slug":629,"type":15},{"name":577,"slug":26,"type":15},{"name":631,"slug":31,"type":15},{"name":633,"slug":634,"type":15},"2026-07-22T05:35:32.342548",{"slug":671,"name":671,"fn":672,"description":673,"org":674,"tags":675,"stars":635,"repoUrl":636,"updatedAt":679},"cayenne-modeler","manage Cayenne projects with CayenneModeler","Use this skill when the user explicitly wants to open CayenneModeler (the GUI) on a Cayenne project, or when the modeling task is inherently visual — reverse engineering (delegated to cayenne-db-import), bulk relationship layout, multi-entity visual refactoring. Trigger on phrases like 'open the Modeler', 'open in CayenneModeler', 'launch the GUI', 'edit visually', 'show me the project in the Modeler'. Do NOT trigger as a fallback for ordinary a-la-carte XML edits — those belong in the cayenne-modeling skill, which is faster and doesn't require the user to context-switch.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[676,677,678],{"name":628,"slug":629,"type":15},{"name":631,"slug":31,"type":15},{"name":633,"slug":634,"type":15},"2026-07-12T08:32:37.199428",{"slug":681,"name":681,"fn":682,"description":683,"org":684,"tags":685,"stars":635,"repoUrl":636,"updatedAt":689},"cayenne-modeling","edit and extend Cayenne ORM models","Use this skill whenever the user wants to edit, inspect, or extend the Cayenne ORM model in a project — adding or modifying entities, attributes, relationships, embeddables, named queries, stored procedures, or DataNodes. Trigger on phrases like 'add an ObjEntity', 'add a DbEntity', 'add a relationship', 'expose this column as an attribute', 'create a new DataMap', 'add a named query', 'create an embeddable', 'add a stored procedure', 'change the attribute type', 'mark this column as nullable', 'rename this entity', or any mention of a Cayenne `*.map.xml` or `cayenne-*.xml` file. Also trigger when the user references modeling concepts (ObjEntity, DbEntity, ObjAttribute, DbAttribute, ObjRelationship, DbRelationship, Embeddable, dbEntityName, deleteRule, db-attribute-path, db-relationship-path, defaultPackage) in the context of a Cayenne-using app. This is the *primary* skill for a-la-carte ORM model manipulation — direct XML edits, not the Modeler GUI.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[686,687,688],{"name":577,"slug":26,"type":15},{"name":631,"slug":31,"type":15},{"name":633,"slug":634,"type":15},"2026-07-19T05:40:32.6889",{"slug":691,"name":691,"fn":692,"description":693,"org":694,"tags":695,"stars":635,"repoUrl":636,"updatedAt":700},"cayenne-query","write and modify Cayenne database queries","Use this skill whenever the user wants to write or modify a Cayenne query — fetching entities by criteria, joining, prefetching to avoid N+1, ordering, paginating, aggregating, or running raw SQL through Cayenne. Trigger on phrases like 'query for X', 'fetch all artists where ...', 'write an ObjectSelect', 'use SQLSelect', 'use SelectById', 'add a prefetch', 'get distinct values', 'count rows', 'find by ID', 'load by primary key', 'build a Cayenne expression', 'why am I getting N+1', 'how do I paginate', 'select a single column', 'select columns into a DTO', 'named query in the DataMap'. Do NOT trigger for modeling changes (use cayenne-modeling) or runtime bootstrap (use cayenne-runtime).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[696,697,698,699],{"name":577,"slug":26,"type":15},{"name":631,"slug":31,"type":15},{"name":633,"slug":634,"type":15},{"name":562,"slug":563,"type":15},"2026-07-12T08:32:35.072322",108]