← Back to Skills Marketplace
hosuke

Clawlendar

by Huang Geyang · GitHub ↗ · v0.3.1 · MIT-0
cross-platform ✓ Security Clean
282
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install clawlendar
Description
Timestamp-first perpetual calendar interop for AI agents. Use when agents need cross-calendar conversion (Gregorian/Julian/ISO/ROC/Buddhist/Japanese era/sexa...
README (SKILL.md)

Clawlendar

Overview

Provide a single, agent-friendly bridge layer so different tools can ask calendar questions in a common schema and receive normalized JSON. Treat this skill as the date interoperability baseline for multi-agent ecosystems.

Workflow

  1. Call capabilities first to discover supported calendars, optional providers, and locale support.
  2. For calendar conversion, parse source payload in declared calendar and bridge through Gregorian.
  3. For instant-based workflows, use timeline (timestamp-first) instead of direct date conversion.
  4. Use calendar_month when UI needs true month boundaries in non-Gregorian systems.
  5. Use day_profile for one-call details (sexagenary, solar_term_24, chinese_lunar, optional astro, optional metaphysics).
  6. Always pass locale (en, zh-CN, zh-TW) when user-facing text is required.

Quick Start (MCP Server)

Install and run as an MCP server for Claude Desktop / Claude Code:

python3 -m pip install -U "clawlendar[all]"
clawlendar

One-line registration in Claude Code:

python3 -m pip install -U "clawlendar[all]" && claude mcp add clawlendar -- clawlendar

Or run directly from source:

pip install -e .
python -m clawlendar.server

CLI Usage

List supported calendars and optional backends:

pip install -e .
python3 scripts/calendar_bridge.py capabilities

Convert one date into multiple targets:

python3 scripts/calendar_bridge.py convert \
  --source gregorian \
  --targets julian,iso_week,minguo,buddhist,japanese_era,sexagenary,solar_term_24 \
  --date-json '{"year": 2026, "month": 3, "day": 9}'

Normalize one instant with timestamp-first model (external time wheel):

python3 scripts/calendar_bridge.py timeline \
  --input-json '{"timestamp": 1773014400}' \
  --timezone 'Asia/Taipei' \
  --date-basis local \
  --targets minguo,japanese_era,sexagenary,solar_term_24

Generate an astro snapshot for zodiac wheel rendering:

python3 scripts/calendar_bridge.py astro \
  --input-json '{"timestamp": 1773014400}' \
  --timezone 'Asia/Taipei'

Get true month boundaries for non-Gregorian month mode:

python3 scripts/calendar_bridge.py calendar-month \
  --source minguo \
  --month-json '{"year":115,"month":3}'

Get unified daily profile payload:

python3 scripts/calendar_bridge.py day-profile \
  --input-json '{"timestamp": 1773014400}' \
  --timezone 'Asia/Taipei' \
  --locale 'zh-TW'

Include full metaphysics block (Bazi/Huangli + Western almanac):

python3 scripts/calendar_bridge.py day-profile \
  --input-json '{"timestamp": 1773014400}' \
  --timezone 'Asia/Taipei' \
  --locale 'zh-CN'

HTTP API

Run HTTP API for multi-claw integration:

pip install -e ".[api]"
./scripts/run_api.sh

Run with Docker:

docker build -t clawlendar:mvp .
docker run --rm -p 8000:8000 clawlendar:mvp

Contract

Use the JSON contract in references/integration-contract.md for tool-to-tool integration. Keep payload keys calendar-specific and avoid ambiguous fields.

Tool Mapping

  • MCP tools: capabilities, convert, timeline, astro_snapshot, calendar_month, day_profile
  • CLI commands: capabilities, convert, timeline, astro, calendar-month, day-profile
  • FastAPI endpoints: GET /capabilities, POST /convert, POST /timeline, POST /astro, POST /calendar-month, POST /day-profile

References

  • Use references/integration-contract.md for request/response schema and compatibility guidance.
  • Use references/calendar-landscape.md for East/West major calendar systems and rollout priorities.
  • Use references/time-wheel-model.md for timestamp-first design and instant/date projection rules.
  • Use references/mvp-release-notes.md as GitHub release draft baseline.

Notes

  • Treat Gregorian as the canonical bridge format.
  • Return warnings instead of hard-failing for optional providers that are not installed.
  • Mark approximate outputs explicitly (for example, sexagenary year boundaries and fixed-date solar-term approximation).
  • Treat timeline as the default bridge for multi-agent scheduling and event processing.
  • chinese_lunar conversion payload is numeric; Chinese textual month/day labels are exposed via day_profile.metaphysics.eastern.lunar_date when lunar_python is available.
Usage Guidance
This skill appears coherent for a calendar interoperability tool. Before installing or running the package it references: 1) verify the correct project/repo name and source (the SKILL.md references a GitHub repo name that slightly differs from the skill slug); 2) if you will pip install "clawlendar[all]", confirm the PyPI package or GitHub release is the intended project and, when possible, review the package contents or Dockerfile for unexpected network or filesystem actions; 3) avoid running installs in privileged or production environments without review; and 4) if you plan to enable agent-autonomous use of this skill, remember the agent could run its documented CLI/API commands — treat the package like any third-party code and review its source if you require high assurance.
Capability Analysis
Type: OpenClaw Skill Name: clawlendar Version: 0.3.1 The clawlendar skill is a comprehensive calendar interoperability utility designed for AI agents to convert between various systems (Gregorian, Lunar, Islamic, etc.) and normalize timelines. The SKILL.md and _meta.json files describe legitimate functionality for MCP servers, CLI tools, and HTTP APIs, with no evidence of malicious intent, data exfiltration, or prompt-injection attacks.
Capability Assessment
Purpose & Capability
Name/description align with the documented functionality (cross-calendar conversions, timeline, day profiles). The declared runtime requirements (python3, pip) are reasonable for a Python calendar package. Minor inconsistency: the homepage/project name in the SKILL.md ('Clawlender' on GitHub) differs slightly from the skill name/slug ('Clawlendar'), which is worth verifying but does not indicate malicious intent.
Instruction Scope
SKILL.md confines instructions to installing/running the calendar package, using its CLI, or running an HTTP API/Docker container. It does not instruct reading unrelated files, exporting credentials, or contacting unexpected external endpoints. The docs do instruct the user/agent to pip install packages and run commands — expected for an instruction-only Python tool.
Install Mechanism
The registry contains no automated install spec (lower baseline risk), but the documentation instructs pip install and optionally docker build/run. Installing via pip or docker will fetch and execute third-party code; this is normal for Python tools but the user should verify the package source (PyPI package or GitHub) and inspect release contents before installing in sensitive environments.
Credentials
The skill declares no required environment variables, no credentials, and no config paths. That is proportional to the stated calendar conversion purpose.
Persistence & Privilege
always is false and the skill is user-invocable only. It does not request permanent inclusion or modification of other skills' configurations. Autonomous invocation by the agent is allowed by default (not a red flag here).
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install clawlendar
  3. After installation, invoke the skill by name or use /clawlendar
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.3.1
clawlendar 0.3.1 - Version bump from 0.3.0 to 0.3.1. - No other changes detected.
v0.3.0
- Added timestamp-first perpetual calendar interop, supporting multi-calendar conversion and normalized timeline processing. - Introduced unified JSON schema for Gregorian, Julian, ISO, ROC, Buddhist, Japanese era, sexagenary, solar terms, and optional lunar, Islamic, Hebrew, and Persian calendars. - Added support for true month boundaries, day-level profiles with Bazi/Huangli/Western almanac fields, and locale-aware outputs. - Provided CLI, HTTP API, and MCP server modes, plus Docker integration for deployment. - Included clear contract references and workflow guidance for agent-based tool interoperability. - Improved handling of approximate outputs and optional provider warnings.
Metadata
Slug clawlendar
Version 0.3.1
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 2
Frequently Asked Questions

What is Clawlendar?

Timestamp-first perpetual calendar interop for AI agents. Use when agents need cross-calendar conversion (Gregorian/Julian/ISO/ROC/Buddhist/Japanese era/sexa... It is an AI Agent Skill for Claude Code / OpenClaw, with 282 downloads so far.

How do I install Clawlendar?

Run "/install clawlendar" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Clawlendar free?

Yes, Clawlendar is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Clawlendar support?

Clawlendar is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Clawlendar?

It is built and maintained by Huang Geyang (@hosuke); the current version is v0.3.1.

💬 Comments