agntcms-content-fs

Read and write JSON content files under content/drafts/ and content/pages/.

Updated May 29, 2026
One-click install
npx skills add https://github.com/AlexHramovich/fr-preview-migration --skill agntcms-content-fs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agntcms-content-fs
Source: https://github.com/AlexHramovich/fr-preview-migration/tree/main/.claude/skills/content-fs
Command: npx skills add https://github.com/AlexHramovich/fr-preview-migration --skill agntcms-content-fs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines content editing by leveraging native file tools for JSON manipulation under the filesystem content adapter, eliminating the need for complex CRUD operations.

Core Features & Use Cases

  • Filesystem Editing: Edit JSON files directly under content/drafts/ and content/pages/ using native file tools.
  • Draft/Publish Workflow: Facilitates a controlled draft-to-publish workflow, maintaining version history and git integration.
  • Use Case: For a developer working with a default filesystem content adapter, this Skill allows for efficient JSON-based content management, avoiding the overhead of traditional CRUD tools.

Quick Start

Use the agntcms-content-fs skill to load a draft of the 'home' page and make changes, then publish it using the admin UI or the draft publish API endpoint.

Frequently Asked Questions about agntcms-content-fs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage JSON content editing directly within the filesystem?

Filesystem content editing is managed by reading and writing JSON files directly under content/drafts/ and content/pages/ directories. This approach uses native file tools to bypass complex CRUD operations for direct JSON manipulation.

What is the draft-to-publish workflow for filesystem content management?

The draft-to-publish workflow involves editing JSON files in content/drafts/ and publishing them to content/pages/. It maintains version history and integrates git commits to track changes for controlled content release.

How does version control work with JSON content files?

Version control for JSON content files works through git integration. As you execute the draft-to-publish workflow, the system maintains version history by creating git commits to track all content modifications.

Do I need filesystem and JSON parsing capabilities to use this content adapter?

Yes, you need access to filesystem and JSON parsing capabilities to use this filesystem content adapter. These prerequisites allow native file tools to read, write, and manipulate the JSON files in drafts and pages directories.

What is the best way to avoid complex CRUD operations for JSON content publishing?

The best way to avoid complex CRUD operations is using a filesystem adapter for JSON manipulation. By editing files directly under content/drafts/ and content/pages/, you leverage native file tools to streamline content publishing without database overhead.