content-management_skill

This skill helps you manage Kuroco content CRUD operations efficiently with best practices for topics, extensions, filtering, and exports.

0

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill diverta/kuroco-skills --skill content-management

  • metadata.json104 B
  • SKILL.md10.1 KB

Overview

This skill documents best practices for Kuroco content management (CRUD) focused on Topics, TopicsGroup, categories, and extensible fields. It explains how to create, retrieve, update, delete, filter, and bulk-upsert content while covering file upload, CSV import, and publish scheduling. The guidance emphasizes predictable API usage and practical patterns for performance and maintainability.

How this skill works

It describes the Topics API operations (list, details, insert, update, delete, bulk_upsert) and the typical JSON shapes returned by list/details calls, including ext_col_* custom fields. It details filter and order_by query construction, pagination using pageID and cnt, and file or CSV workflows (upload then attach via ext_col). It also explains publish flags, open_ymd/close_ymd reservation, tags, and related-content linking via topics_id.

When to use it

  • When defining a new content type (TopicsGroup) or adding ext_col custom fields
  • When implementing list or detail endpoints using filter and order_by for public pages
  • When performing create, update, delete, or bulk_upsert operations from admin tools or import scripts
  • When attaching files or images to content via the files upload API before insert/update
  • When scheduling content with open_ymd/close_ymd or restricting visibility with topics_flg and access controls

Best practices

  • Model content with a clear TopicsGroup → Category → Topics hierarchy and keep ext_col naming consistent (ext_col_01..ext_col_99)
  • Send only fields you want to change on update requests; use insert/update endpoints per Topics API patterns
  • Use filter queries (contains, in, >=, <=) and compound logic to minimize client-side filtering and keep API responses small
  • Leverage caching (e.g., one-day TTL) and clear cache on updates; use pageID and cnt for pagination to avoid huge payloads
  • Upload files first to get file_id, then reference them in ext_col file fields; prefer CSV bulk_upsert for large imports and validate data before uploading

Example use cases

  • Create a news article with subject, contents (WYSIWYG), tags, category_id, ext_col custom fields, and reservation using open_ymd/close_ymd
  • Fetch a filtered, paginated list of published topics: filter=(category_id = 1 or tag contains 'event') and topics_flg = 1, order_by=ymd desc, pageID=1, cnt=10
  • Update a single field on an existing topic by sending only the changed ext_col or subject to /{content}/update/{topics_id}
  • Bulk import articles from CSV using /{content}/bulk to upsert many Topics and link images by pre-uploaded file_id
  • Attach related content by saving ext_col_X as {topics_id, subject} so front-end can render content relationships

FAQ

Set open_ymd to the desired start date and optionally close_ymd for an end date; ensure topics_flg is set to 1 for public visibility when the window is active.

Can I filter by tags or custom fields?

Yes. Use filter with contains for text or tag arrays, and reference ext_col_N for custom fields. Combine conditions with and/or and use order_by for sorting.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational