remove-demo-limits

Name: remove-demo-limits
Availability: InStock
Author: arth

Remove managed-template demo restrictions from self-hosted forks.

1|Updated Apr 19, 2026

Search Tags:#tests #self-hosting #demo limits #fork cleanup #auth gating #session caps #message deletion

Ready to run

npx skills add https://github.com/arthtyagi/onloop --skill remove-demo-limits-arthtyagi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: remove-demo-limits
Source: https://github.com/arthtyagi/onloop/tree/main/.agents/skills/remove-demo-limits
Command: npx skills add https://github.com/arthtyagi/onloop --skill remove-demo-limits-arthtyagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes managed-template demo restrictions from a fork so a self-hosted deployment can behave like a normal product instead of a trial environment.

Core Features & Use Cases

Restriction Removal: Eliminates session caps, message caps, hosted-only gating, and message deletion blockers.
Code Cleanup: Removes or simplifies dead helper code and stale tests that only exist to support the hosted demo flow.
Fork Customization: Fits maintainers who want their fork to run without Open Harness trial constraints while keeping unrelated auth and sandbox behavior intact.

Quick Start

Use this skill to remove the demo restrictions from your fork, clean up any now-unused helper code, and verify the updated repository still behaves correctly.

Frequently Asked Questions about remove-demo-limits

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I remove demo limits from a forked template for self-hosting?▼

Removing session caps from a self-hosted fork requires editing route guards and auth callbacks to bypass managed-template restrictions. This preserves unrelated sandbox behavior while eliminating hosted trial constraints.

What are managed-template demo restrictions in a forked repository?▼

Managed-template demo restrictions are hosted-only gating mechanisms that enforce session caps, message caps, and message deletion blockers. They exist to support a trial environment flow and limit forked repository functionality.

How do I clean up dead helper code and stale tests after removing trial caps?▼

Cleaning up dead helper code and stale tests after removing trial caps involves removing or simplifying functions that only supported the hosted demo flow. You must then verify the updated repository still behaves correctly without these restrictions.

Can I remove message deletion blockers and auth gating without breaking session behavior?▼

You can remove message deletion blockers and auth gating without breaking session behavior by applying coordinated edits to route guards and auth callbacks. This process preserves unrelated session and sandbox behavior intact while removing restrictions.

Does removing hosted demo restrictions require updating route guards and auth callbacks?▼

Removing hosted demo restrictions does require updating route guards and auth callbacks to eliminate hosted-only gating. Coordinated edits across helper code and tests are necessary to ensure the fork behaves like a normal product.