GenCMS is iGears' model-agnostic AI workspace and runtime direction for building assistants, document extraction, content and internal agent solutions on an organisation's own data.

It is for developers and organisations that need custom or privately deployed AI with explicit tenant, data and permission boundaries.

Account and tenant administration, workspace records, scoped API keys and Guard scanning are available. Composer can run through a tenant's region-locked AIHK or AICA gateway after its AI key is ready.

Request managed workspace access or ask iGears to scope a 30-day MVP. Project services are fixed-price, with the scope, fee and acceptance checks stated in a quotation.

Developers preview

Package a capability once.

Preview the proposed Skill package format: a manifest, prompt or handler, input and output schemas and tests. Guard scanning is available; the SDK, CLI login and marketplace publishing flow are not released yet.

Skill CLI API reference

Product preview — commands and publishing steps below document the intended developer experience and are not available as a released GenCMS SDK or CLI. Public Guard scans can be used today.

Skill CLI

Proposed path from empty folder to published Skill.

The planned CLI would scaffold a package, test it and submit it for Guard review. These commands are illustrative and not released.

1
gencms skill init — scaffold the package
2
gencms skill run — test locally against real input
3
gencms skill test --models gpt,claude,gemini
4
gencms skill scan — run Guard before you submit
5
gencms skill publish — submit for review

skill.json

{
  "name": "seo-audit",
  "version": "3.0.1",
  "publisher": "gencms",
  "category": "Marketing",
  "execution": { "mode": "auto" },
  "permissions": ["web.fetch", "memory.read"],
  "input":  { "url": "string", "depth": "number?" },
  "output": { "score": "number", "findings": "Finding[]" },
  "pricing": { "type": "paid", "tier": "pro" }
}

planned-cli-example

npm i -g @gencms/cli
gencms login
gencms skill init seo-audit
gencms skill scan ./seo-audit
gencms skill publish ./seo-audit

Package structure

Inspectable by design.

The proposed package design keeps the manifest, capability, schemas and tests available for review before any future installation.

manifest

Name, version, permissions, execution mode, pricing.

handler / prompt

The actual capability — a prompt template or a code handler.

schemas

Typed input and output so a Workflow can rely on the shape.

tests

Sample inputs with expected properties, intended to run during a future publish review.

docs

What it does, sample input, sample output, limits.

changelog

What changed between versions, intended for a future published Skill page.

Open format

The package design is readable.

The current documentation describes the proposed package shape and validation rules. Catalogue entries are unpublished concepts, not released packages or reference implementations.

Package specification

Layout, manifest fields, permissions, schemas, tests and what validation rejects.

Manifest reference

Every field in skill.yaml and what it controls.

Catalogue concepts

Inspect unpublished capability ideas and their proposed permissions; none are downloadable or executable packages yet.

Publishing roadmap

Proposed free, paid and private options.

Free

Proposed: a publicly listed package with no package fee. Credit metering and publisher earnings are not implemented.

Paid

Proposed: one-time, subscription or credit-premium packaging. Billing and entitlement are not implemented.

Private

Proposed: organization-only publishing without a public listing. Private package publishing is not implemented.