push-page-cms — community push-page-cms, community, ide skills

v1.0.0
GitHub

About this Skill

Ideal for Frontend Agents needing dynamic page management and CMS integration. Posts page data into the Pure CMS pages table and optionally updates header comp links. Use when adding a new dynamic page, pushing page content to CMS, or ensuring a page link appears in the header n

shishiv30 shishiv30
[0]
[0]
Updated: 2/26/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
28
Canonical Locale
en
Detected Body Locale
en

Ideal for Frontend Agents needing dynamic page management and CMS integration. Posts page data into the Pure CMS pages table and optionally updates header comp links. Use when adding a new dynamic page, pushing page content to CMS, or ensuring a page link appears in the header n

Core Value

Empowers agents to push page data to CMS and update header links using pure JavaScript, leveraging route configurations and CMS page naming conventions, and integrating with server-side configurations like server/configs/page.js.

Ideal Agent Persona

Ideal for Frontend Agents needing dynamic page management and CMS integration.

↓ Capabilities Granted for push-page-cms

Pushing dynamic page content to CMS for centralized management
Updating header links for new pages served at /page/:key routes
Automating page data file management in data/page/<name>.js format

! Prerequisites & Limits

  • Requires server-side configuration access
  • Limited to JavaScript-based implementations
  • Dependent on CMS compatibility and API access

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is push-page-cms?

Ideal for Frontend Agents needing dynamic page management and CMS integration. Posts page data into the Pure CMS pages table and optionally updates header comp links. Use when adding a new dynamic page, pushing page content to CMS, or ensuring a page link appears in the header n

How do I install push-page-cms?

Run the command: npx killer-skills add shishiv30/pure/push-page-cms. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for push-page-cms?

Key use cases include: Pushing dynamic page content to CMS for centralized management, Updating header links for new pages served at /page/:key routes, Automating page data file management in data/page/<name>.js format.

Which IDEs are compatible with push-page-cms?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for push-page-cms?

Requires server-side configuration access. Limited to JavaScript-based implementations. Dependent on CMS compatibility and API access.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add shishiv30/pure/push-page-cms. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use push-page-cms immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

push-page-cms

Install push-page-cms, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Push Page Data to CMS and Update Header Links

Use this workflow when you add a new dynamic page (served at /page/:key) and want its content in the CMS and a nav link in the header.

How dynamic pages work

ItemValue
RouteGET /page/:key (e.g. /page/index, /page/about)
Configserver/configs/page.js — fetches by key
CMS page namepage${key}.toLowerCase() (e.g. index → pageindex)
Page data filedata/page/<name>.js (e.g. data/page/index.js, data/page/ai-trend.js for key ai-trend) — default export: array of sections
Header comp keyheader — link shape: { id, text, path, order, parentId }; path for page = /page/<key>

Main app fetches: GET {cmsUrl}/api/pages/content/{pageName} and GET {cmsUrl}/api/comp/public/header.

Step 1: Post page data to CMS

Script (recommended): cms/scripts/seed-and-sync.js

Seeds local DB from data/page/*.js (pages from pagePath in data/page/header.js) and data/theme.js, then syncs to remote CMS.

bash
1# From repo root
2node cms/scripts/seed-and-sync.js [--local-only] [CMS_URL] [CMS_EMAIL] [CMS_PASSWORD]
  • --local-only — Seed local DB only.
  • With credentials — Seeds local, then syncs to remote via API.

Without script: Use CMS API (admin auth): POST /api/pages — body: { name, title, type: "json", data, meta, status }. Page name = key (e.g. index, ai-trend). Add page key to pagePath in data/page/header.js for seed-and-sync to include it.

If you use --update-header, the script:

  1. Reads current header comp (API or DB).
  2. Ensures there is a link with path: '/page/<key>'; adds one if missing (text = page title or key, order = after existing).
  3. Writes the updated links back to the comp header.

Manual update: Edit data/page/header.js to add a link, then run node cms/scripts/seed-and-sync.js to sync.

Checklist

  • Page data file exists (e.g. data/page<key>.js or data/page/<name>.js) with default export = section array.
  • Add page to pagePath in data/page/header.js, add data/page/<key>.js, run node cms/scripts/seed-and-sync.js.
  • Main app has CMS_URL set so it can fetch the page and header from CMS.

Reference

  • Dynamic page route and config: server/routes/page.js, server/configs/page.js
  • Page section order and helpers: helpers/pageData.js (arrayToPageData, PAGE_SECTIONS_ORDER)
  • Seed and sync: cms/scripts/seed-and-sync.js; header and pages: data/page/header.js
  • CMS pages API: cms/routes/pages.js (POST /api/pages, PUT /api/pages/:id)
  • CMS comp API: cms/routes/comp.js (GET /api/comp/public/:key, POST /api/comp)

Related Skills

Looking for an alternative to push-page-cms or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer