← Back to Skills Marketplace
139
Downloads
0
Stars
0
Active Installs
6
Versions
Install in OpenClaw
/install openclaw-laravel-creem-agent-skill
Description
Creem payment store assistant — query subscriptions, customers, transactions, products, run heartbeat checks, and manage a payment store via a local Laravel...
Usage Guidance
This skill is coherent with its purpose but can perform real payment-store actions by forwarding user text to a local HTTP endpoint. Before installing: 1) Verify that the Laravel Creem Agent service at 127.0.0.1:8000 is the trusted local service you expect and is not exposed to external networks. 2) Ensure the endpoint requires appropriate authentication/ACLs and that the agent host is secured. 3) Consider disabling autonomous invocation for this skill or require explicit confirmation for destructive intents (cancel/create) in OpenClaw to prevent accidental changes. 4) Test using read-only queries first and enable audit/logging on the endpoint so you can review actions the agent performed. 5) If you use channels (Telegram) follow OpenClaw docs to restrict who can send commands. If you want, provide the endpoint's access controls or a read-only mode and I can suggest concrete guardrails.
Capability Analysis
Type: OpenClaw Skill
Name: openclaw-laravel-creem-agent-skill
Version: 1.0.5
The skill acts as a functional bridge between the OpenClaw agent and a local Laravel-based payment management service (Creem Agent). It uses curl to interact with a local HTTP endpoint (127.0.0.1:8000) to query store data like transactions and subscriptions. The instructions in SKILL.md are designed to ensure the agent prioritizes the tool over its internal knowledge and correctly handles JSON escaping, with no evidence of data exfiltration, malicious execution, or unauthorized system access.
Capability Assessment
Purpose & Capability
The name/description match the behavior in SKILL.md: all actions are routed to a hard‑wired local Laravel endpoint. The only required binary is curl, which is appropriate for the described HTTP forwarding behavior.
Instruction Scope
SKILL.md strictly instructs the agent to POST user text to http://127.0.0.1:8000/creem-agent/chat and relay the endpoint's `response` verbatim. It does not read files or extra env vars. Note: the endpoint supports management intents (cancel_subscription, create_checkout, switch_store, etc.), so forwarded user text can result in state‑changing or destructive operations if not constrained or confirmed.
Install Mechanism
Instruction-only skill with no install spec and no code files. This is low-risk from an install perspective — nothing is downloaded or written by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. README mentions general OpenClaw/Telegram configuration but those are not required by the skill itself and are typical for OpenClaw deployments.
Persistence & Privilege
always:false (not force-included). The platform default allows autonomous invocation, so the agent could call this skill without user confirmation — combined with the endpoint's ability to perform management actions, this raises an operational-risk consideration (accidental/cascading changes) but it is not an incoherence in the skill design.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install openclaw-laravel-creem-agent-skill - After installation, invoke the skill by name or use
/openclaw-laravel-creem-agent-skill - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.5
- Clarified intent preservation: Added explicit rules to maintain measurement, time, status, and ranking phrases from user questions.
- Expanded routing heuristics: Detailed new routing table and fallback rules to ensure precise query forwarding and accurate aggregation.
- Improved count handling: Specified that when a list is returned for a count/quantity question, count the items and reply with the number, not the raw list.
- Added and strengthened anti-patterns: Explicitly prohibit relaying transaction lists when a count is asked for, and clarified other disallowed behaviors.
- Reorganized and streamlined documentation for easier reference and improved precision during multi-step query handling.
v1.0.4
openclaw-laravel-creem-agent-skill 1.0.4 changelog
- Clarified that all store, payment, and subscription queries must be sent to the Laravel endpoint first.
- Added rules prohibiting fallback to local data, workspace files, saved notes, or database exports before calling the Laravel endpoint.
- Explicitly disallow generic disclaimers about missing local context or data when answering store-related questions.
- Enhanced anti-pattern and precision rules to prevent asking users about transaction storage or data sources before calling the endpoint.
- Updated multi-step query examples and rules to reinforce endpoint-first behavior.
v1.0.3
- Updated instructions to emphasize sending the user's exact question to the endpoint without simplification, especially for filtered/count questions (e.g., time periods, success/failure status).
- Added a new "Routing heuristics for low-cost models" section with detailed examples and anti-patterns to avoid over-generalizing user queries.
- Clarified that for multi-step queries, the exact question should be forwarded first, and only fallback to intent decomposition if the endpoint cannot answer directly.
- Introduced new "Precision rules" requiring important qualifiers (like "successful", "today", "top") to be preserved when forwarding.
- Strengthened prohibition against answering or replacing user queries with assistant reasoning when the endpoint can answer them.
- No file or implementation changes—documentation update improving query fidelity and robustness.
v1.0.2
Version 1.0.2
- Documentation streamlined: Removed operator override instructions (`AGENT_URL`), making endpoint, curl examples, and setup simpler.
- Quick self-test and usage examples now use the hardcoded local endpoint URL for clarity.
- No changes to source code or functional behavior; update is limited to documentation cleanup.
v1.0.1
- Default endpoint is now `http://127.0.0.1:8000/creem-agent/chat`; environment variable `AGENT_URL` is optional.
- Updated curl command examples to fall back to the default endpoint if `AGENT_URL` is not set.
- Environment variable requirement for `AGENT_URL` removed from metadata; only `curl` is now required.
- Updated documentation for endpoint configuration and connection instructions.
- No code or logic changes—documentation and metadata only.
v1.0.0
openclaw-laravel-creem-agent-skill 1.0.0 – Initial Release
- Introduces an assistant to manage and query Laravel Creem payment stores via a local HTTP endpoint.
- Supports subscription, customer, transaction, product queries, and store monitoring (heartbeat).
- Handles both single-intent and multi-step workflows through chained endpoint calls.
- Ensures all store/payment questions are answered strictly via the configured HTTP endpoint.
- Includes setup requirements, usage guidance, example curl calls, and best-practice rules for error handling and multi-store scenarios.
Metadata
Frequently Asked Questions
What is Laravel Creem Agent?
Creem payment store assistant — query subscriptions, customers, transactions, products, run heartbeat checks, and manage a payment store via a local Laravel... It is an AI Agent Skill for Claude Code / OpenClaw, with 139 downloads so far.
How do I install Laravel Creem Agent?
Run "/install openclaw-laravel-creem-agent-skill" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Laravel Creem Agent free?
Yes, Laravel Creem Agent is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Laravel Creem Agent support?
Laravel Creem Agent is cross-platform and runs anywhere OpenClaw / Claude Code is available (linux, darwin).
Who created Laravel Creem Agent?
It is built and maintained by romansh (@romansh); the current version is v1.0.5.
More Skills