home / skills / openclaw / skills / coding-agent-user-rules

coding-agent-user-rules skill

/skills/mpaicoding-byte/coding-agent-user-rules

This skill helps you undo accidental publications by guiding unpublish steps, revoking visibility, and restoring previous versions across platforms.

npx playbooks add skill openclaw/skills --skill coding-agent-user-rules

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
158 B
---
name: coding-agent-user-rules
description: Mistakenly published, don't know how to unpublish ;(
---

Mistakenly published, don't know how to unpublish ;(

Overview

This skill provides an archived snapshot of all versions of a Python-based coding agent and its user rules. It was published inadvertently and is intended as a record rather than an active, supported integration. The skill can help you locate historical rule sets and metadata for auditing or backup purposes.

How this skill works

The skill exposes archived files, version history, and metadata for the coding agent user rules so you can inspect past states and changes. It does not run code or provide live enforcement; it simply surfaces the stored artifacts and commit history for review. Use it to audit, diff, or export rule sets for migration or deletion.

When to use it

  • You need to review historical versions of user rules for audit or compliance.
  • You want to extract and migrate archived rules into a supported system.
  • You need to confirm what was published by mistake before taking removal steps.
  • You want a backup of rule sets prior to permanent deletion or unpublishing.
  • You are investigating accidental publication and need context to contact platform support.

Best practices

  • Treat the archive as read-only—export or copy the artifacts before editing elsewhere.
  • Document the reason and timeframe for the accidental publish before requesting removal.
  • Gather identifying metadata (skill name, version, timestamps, account info) to speed up support requests.
  • Check platform support docs or contact channels first; provide a concise, factual request to unpublish.
  • If sensitive data was exposed, follow your organization’s incident response and data-removal procedures immediately.

Example use cases

  • Auditor retrieves previous rule versions to verify when a policy changed.
  • Developer exports the archived rules to recreate a corrected, private version in a different repo.
  • Product owner documents the accidental publish event and collects timestamps and artifacts for support.
  • Security lead confirms whether any sensitive data was included in the published artifacts.

FAQ

How do I unpublish this skill?

Contact the hosting platform’s support with the skill identifier, account details, and a brief description asking for removal; include timestamps and any sensitive-file indicators to prioritize the request.

Can I delete sensitive files from the archive myself?

If the platform allows edits, update or remove files and republish; otherwise, escalate to platform support and follow your internal incident-removal steps.

Is this skill still active or executable?

No—this skill is an archive of artifacts and is not intended to run. Use it only for review, export, or forensic purposes.