← Back to Skills Marketplace
Website Manager
by
Prompt Circle
· GitHub ↗
· v1.0.6
· MIT-0
137
Downloads
1
Stars
0
Active Installs
7
Versions
Install in OpenClaw
/install website-manager
Description
Create, recreate, redesign, publish, and operate websites managed from Notion, including blogs, CMS-driven sections, widgets, filtering/search interactions,...
Usage Guidance
This skill appears to do what it says: blueprint sites, create/sync a Notion CMS, validate built output, and optionally deploy to Netlify. Before using it: 1) Only provide NOTION_ACCESS_TOKEN / NOTION_TOKEN and NETLIFY_AUTH_TOKEN when you explicitly ask the agent to provision CMS or run automated deploys. 2) Use least-privileged tokens (Notion internal integration shared to a single parent page; Netlify token limited to deploy scope). 3) Review .website-manager/notion.json and .website-manager/deploy.json before committing or syncing them — they should contain IDs/URLs only. 4) Remember the scripts will create remote resources (databases/pages on Notion, sites/deploys on Netlify); run them in a safe/test workspace first and revoke tokens when finished if you have concerns. 5) The runtime_metadata slightly inconsistently lists Netlify as a primary credential as well; confirm with the maintainer if you need stricter metadata before automated use.
Capability Analysis
Type: OpenClaw Skill
Name: website-manager
Version: 1.0.6
The website-manager skill bundle is a legitimate toolset for automating website creation and management using Notion as a CMS and Netlify for hosting. The Python scripts (create_notion_cms.py and netlify_zip_deploy.py) use standard libraries to interact exclusively with official APIs (api.notion.com and api.netlify.com) and include logic to persist non-secret metadata locally. The instructions in SKILL.md are task-oriented, align with the stated purpose, and include explicit security guidance to avoid storing secrets in repository files or Notion databases.
Capability Assessment
Purpose & Capability
The name/description target Notion-backed site creation, management, and Netlify deployment; the included scripts call only Notion and Netlify APIs and perform site validation and blueprinting — all directly relevant to the stated purpose.
Instruction Scope
SKILL.md explicitly restricts secret usage to user-requested automated CMS provisioning, sync, or deploys. The runtime instructions read local reference files and call helper scripts that perform network operations and write non-secret JSON metadata. This is expected, but those operations will modify remote resources (create Notion databases/pages, create Netlify sites/deploys) and write local runtime files, so user consent is required before performing those privileged actions.
Install Mechanism
No install spec or third-party downloads; scripts are included in the repo and use standard Python stdlib (urllib, zipfile, tempfile). No high-risk remote installs or archived code downloads were found.
Credentials
The primary credential (NOTION_ACCESS_TOKEN) and optional NETLIFY_AUTH_TOKEN are appropriate for the requested operations. Minor metadata inconsistency: SKILL.md metadata lists primaryEnv as NOTION_ACCESS_TOKEN but runtime_metadata.primary_credentials lists both NOTION_ACCESS_TOKEN and NETLIFY_AUTH_TOKEN — this is a small mismatch but not a functional red flag. The skill does not request unrelated secrets.
Persistence & Privilege
The skill will perform outbound network requests and persistent_file_writes (persisting non-secret IDs to .website-manager/*.json) and can create remote resources (Notion DBs, Netlify sites/deploys). always:false (not force-included) and model invocation is allowed (platform default). These privileges match the skill's purpose but warrant explicit user confirmation before automated runs.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install website-manager - After installation, invoke the skill by name or use
/website-manager - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.6
No user-facing changes in this release.
- Internal metadata updated (added skillKey and primaryEnv fields).
- No changes to functionality or workflows.
v1.0.5
**Expanded and clarified credential handling for deployment and provisioning workflows.**
- Added detailed `conditional_env_vars` specifying exactly which credentials are required for different use cases (planning, CMS provisioning, sync, and deployments).
- Introduced `credential_scope_guidance` to encourage least-privilege and minimize unnecessary credential requests.
- No changes to functionality outside credential/metadata structuring; no file or code changes detected.
- No impact on user experience or workflows unless performing automated CMS creation or deployment.
v1.0.4
- Added references/site-types/generic.md as a fallback reference for generic site types.
- Updated credential rules to clarify that secrets should only be requested if the user wants automated provisioning, synchronization, or deployment.
- Minor clarifications in instructions for using reference files, noting generic.md should be used when no specific site type fits.
- Added a note in metadata: credentials are conditional and should only be requested as needed.
v1.0.3
- Added a markdown section describing persisted runtime metadata files, including their default locations and storage guidelines.
- Updated the metadata and runtime metadata sections to include new environment variables (`NETLIFY_ACCOUNT_SLUG`, `NETLIFY_SITE_NAME`) for Netlify deployment.
- No code changes were detected in this release.
v1.0.2
- Improved credential handling for Netlify: now allows deploying without specifying NETLIFY_SITE_ID by auto-creating a new site if needed.
- Clarified that only non-secret site identifiers and URLs are persisted; secrets should never be stored in Notion or repo files.
- Minor edits to documentation for clearer credential rules and deployment flow.
- No functional code changes.
v1.0.1
- Added scripts/create_notion_cms.py to automate creation of the default Notion CMS under a shared parent page.
- Updated SKILL.md to document new credentials, required environment variables, and privileged operations for Notion and Netlify automation.
- Detailed credential-handling rules: now only request Notion or Netlify secrets when automated CMS creation or deploys are needed.
- Expanded helper script documentation to include the new Notion CMS creation script.
- No breaking changes to planning, validation, or content modeling workflows.
v1.0.0
Initial release of website-manager - unified website building and management with Notion CMS support.
- Enables creation, rebuilding, redesign, and ongoing management of websites using Notion as the editorial source.
- Supports static and CMS-driven sections, lightweight publishing workflows, and SEO/AEO/GEO improvements.
- Provides opinionated defaults: plain HTML/CSS/JS stack, Netlify deployment, and portable output with no vendor lock-in.
- Includes modular workflows for widgets, filtering/search, validation, and automation-friendly routines.
- Designed for both technical and non-technical users—minimizes setup choices unless customization is needed.
Metadata
Frequently Asked Questions
What is Website Manager?
Create, recreate, redesign, publish, and operate websites managed from Notion, including blogs, CMS-driven sections, widgets, filtering/search interactions,... It is an AI Agent Skill for Claude Code / OpenClaw, with 137 downloads so far.
How do I install Website Manager?
Run "/install website-manager" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Website Manager free?
Yes, Website Manager is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Website Manager support?
Website Manager is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Website Manager?
It is built and maintained by Prompt Circle (@hollaugo); the current version is v1.0.6.
More Skills