diverta/kuroco-skills
5 skills5 installs5 starsGitHub
Install
npx skills add https://github.com/diverta/kuroco-skillsSkills in this repo
1Kuroco Admin ApiKuroco Admin API is an agent skill for solo builders who manage content on Kuroco, a Japanese headless CMS, and need reliable admin API discovery instead of trial-and-error HTTP calls. It documents how to use the kuroco-admin CLI: advise for goal-to-endpoint guidance when module or controller names are unknown, discover to list modules and controllers programmatically, and help to pull request properties, types, and required fields in JSON Schema form. The skill emphasizes relationships such as topics_group_id before topics operations, and shows when to run exec for extended column schemas. It fits indie teams shipping marketing sites, member portals, or inquiry flows where the agent must list parents, validate payloads, and execute edits safely. Intermediate complexity assumes CMS credentials and basic REST familiarity; outputs are structured API steps and field definitions agents can turn into scripts or one-off maintenance tasks during build and later operate iterations.1installs2Kuroco Api Contentkuroco-api-content is an agent skill for solo builders maintaining sites on Kuroco (RCMS): it documents file upload to the files API, binding file_id into content insert JSON, public image URLs on the Kuroco image host with resize query parameters, and CSV-style bulk upsert against the news bulk endpoint. The readme is JavaScript fetch-oriented with credentials included, which matches admin-authenticated or session-backed workflows common in headless CMS migrations and small agency stacks. Use it during build when you are scripting imports, syncing editorial content from spreadsheets, or wiring file fields on custom columns—not for generic React UI polish. Agents can translate the patterns into your framework’s HTTP client. You still need a Kuroco site key, API paths, and field keys (subject, contents, ymd, topics_flg) matching your schema. Prism catalogs this as integration knowledge, not a hosted connector service.1installs3Kuroco DocsKuroco-docs is an agent skill that packages official Kuroco Headless CMS documentation so solo and indie builders can integrate content APIs without memorizing the product manual. Kuroco positions itself as API-first: you choose features when you need them, connect via APIs managed from the console, and keep your preferred languages and frameworks on the client side. The material covers why teams pick Kuroco (multi-device publishing, integrations with existing services, separated editorial roles, enterprise-grade needs) and points to deeper docs and Slack community support when questions go beyond reference lookup. Install it when your agent is scaffolding content models, planning API consumption, or answering operational questions such as contract termination steps in the admin UI. It matters on Prism because builders evaluating or shipping on Kuroco need citable, journey-aligned placement next to other integration and documentation skills—not a generic popularity ranking.1installs4Kuroco Frontend IntegrationKuroco AI Auto-Deployment streamlines the entire frontend integration pipeline by automating site registration, building frontend artifacts (npm/Nuxt), uploading to S3, and triggering deployment. Developers use it to eliminate manual steps when connecting a frontend to Kuroco's headless CMS. This matters because it reduces deployment friction and ensures consistent, repeatable builds from code to production.1installs5Kuroco Server ProcessingKuroco Server Processing is an agent skill for developers building on the Kuroco headless CMS who need server-side Smarty plugin behavior documented in one place. Solo builders and small teams wiring custom endpoints, template logic, form flows, and third-party hooks can invoke it when the agent must pick the correct plugin from a large surface area—API internal calls, management APIs, credential assignment, AI completions, embeddings, Firestore activity, and Vue-facing template helpers. The skill is organized as a master index plus category markdown files (API plugins, strings, arrays, forms, auth, integrations, files, Vue), so queries resolve to the right symbol instead of hallucinated Kuroco APIs. It sits on the Build integrations shelf because it assumes an existing Kuroco project and focuses on server template processing, not distribution or analytics. Complexity is advanced due to ecosystem size and bilingual doc context; confidence reflects strong readme structure but empty package description field.1installs