Automate Kuroco API design, authentication, and content management workflows.
npx skills add https://github.com/diverta/kuroco-skills --skill kuroco-api-content
Please help me install this Agent Skill. Skill: kuroco-api-content Source: https://github.com/diverta/kuroco-skills/tree/main/skills/api-content Command: npx skills add https://github.com/diverta/kuroco-skills --skill kuroco-api-content
Kuroco API design, authentication handling, and content management require consistent patterns to reduce integration time and mistakes. This Skill provides reusable workflows and reference patterns to accelerate secure API usage and content operations.
Use the kuroco-api-content skill to scaffold and guide Kuroco API integration tasks.
High-intent search queries and answers about installing and using this skill.
Kuroco API authentication is implemented using Cookie, StaticToken, or DynamicToken schemes. You can scaffold the login_challenge and token flow to securely manage user sessions before executing content CRUD operations against the rcms-api.
Filtering Kuroco API content requires applying specific filter queries to the rcms-api endpoints. This approach supports retrieving topics, categories, and custom fields based on defined parameters to streamline content management workflows.
Kuroco API supports both CORS and rate limiting configurations as part of its security setup. These endpoint patterns and security configurations ensure reliable integrations and controlled access to your RCMS API resources.
Yes, the Kuroco admin_api supports content management workflows including topics, categories, and custom fields. It enables reliable content governance and CRUD operations directly through structured API endpoint design patterns.
Frontmatter-based discovery is required for Kuroco API content workflows to satisfy structural requirements for endpoint patterns and security configuration. It ensures consistent design across authentication schemes and content operations.
Static tokens for Kuroco API authentication provide fixed access credentials without dynamic session handling. While suitable for server-to-server integrations, they lack the dynamic user context provided by the login_challenge and DynamicToken flows.
Serg28Create OpenAPI 3.1 YAML specifications with endpoints, schemas, and security.
JingyiWngCreate and manage Databricks vector search endpoints and indexes.
hendrax5Implement frontend UI and integrate it with backend APIs.
NagyViktIntegrate headless CMS platforms with Vercel-hosted applications.
