Skip to content
Skills Library
Programming · Building & coding

rstrbot-plugin-development

/rstrbot-plugin-development

Use when building, reviewing, or documenting RstrBot executable plugins or language SDKs.

Repository
RstrBot ↗
Licence
MIT
Last repository change
30.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 30.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when building, reviewing, or documenting RstrBot executable plugins or language SDKs.

Original author description

Use when building, reviewing, or documenting RstrBot executable plugins or language SDKs.

How it works

  1. Read the contract first
  2. Capability and trust rules
  3. SDK conformance
Original SKILL.md headings · 40 lines, 459 words
SKILL.md preview
---
name: rstrbot-plugin-development
description: Use when building, reviewing, or documenting RstrBot executable plugins or language SDKs.
---

# RstrBot plugin development

## Read the contract first

- In the complete recursive recipe, locate the `rstrbot-plugin-protocol`, `rstrbot-sdk`, and `rstrbot-plugin-host` packages and read their entrypoints, authoritative contracts, and acceptance cases. These are the reconstruction inputs.
- In an existing generated implementation, also read its actual `docs/PLUGIN_PROTOCOL.md` and `sdk/README.md`; those generated files are not prerequisites for consuming this Markdown recipe.
- Choose the existing Rust, Python, TypeScript, or C# SDK. Implement the public protocol; do not depend on private core objects.
- Treat the package manifest, installed package, workspace instance, and one invocation as separate things.

## Capability and trust rules

- A capability declaration describes what a plugin requests; it does not grant permission. The core checks installed declarations and current user authority for each operation.
- Workers are trusted native programs in this release. A separate process is not a malicious-code sandbox. Do not describe it as one.
- Keep provider credentials scoped to the provider call. Ordinary tool invocations must not receive them.
- Do not add worker-initiated core-admin methods, arbitrary executable installation through workspace settings, or network listeners for the local worker protocol.
- Validate initialization context, nonce, protocol version, request IDs, frame limits, method parameters, and the single terminal response. Bound queues and event output.
- Propagate cancellation and stop child processes. Cancellation cannot reverse a remote side effect; retain an unknown/in-flight outcome for reconciliation and never silently replay it.
- Redact keys, authorization headers, private URL paths, and remote response bodies from diagnostics.

## SDK conformance

Keep the current 1.0 reference and vectors unchanged. The extension protocol's 1.1-draft, SDK capability contract, host lifecycle/compatibility contracts, and core extension API describe future negotiated capabilities. Bounded host services grant no core-admin access. Freeze the unmodified compatibility fixtures by digest, then record import, behavior, recovery, and cleanup separately; a verified source hash does not prove compatibility. Update SDK documentation and embedded tutorials with the same distinction.

Build the selected example using the pinned toolchain. In a generated implementation that provides this harness, run:

```sh
python3 tests/plugin_conformance.py --sdk <rust|python|typescript|csharp>
```

For a full local check, use `mise exec -- ./scripts/check.sh` when that script actually exists. Otherwise generate the required harness and record its real command. An unavailable runtime is `not_executed`, not a pass. Update the protocol document, SDK README, and conformance vectors together when changing shared behavior.

For 1.14 provider rejections, use the supplemental PROVIDER_ERRORS contract and four-SDK vectors. Preserve generic fallback for older hosts/workers, never expose response bodies, and do not treat an upstream 401 as local sign-out. Report SDK runtimes not actually tested.

The 1.15 generated implementation is the `generated/rstrbot-implementation/` source submodule. Verify its URL and pinned commit; recipe archives must not include implementation source or Git metadata.

1.29 按 RSTRBOT-38 实测交互及计划运行的工具目录分页、权限和超限错误;工具目录完整性不得扩大授权。

1.30 按 RSTRBOT-39 核对文本附件原文、模型账本、重启、权限和同意图恢复;文本附件不能冒充图片或完整媒体支持。

Versions

The database has no other skills named rstrbot-plugin-development.

Database snapshot: 13.11.2026 · package version d71c2ef05ef2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90rstrbot-development
    Use when changing RstrBot core, web UI, API, persistence, deployment, or repository documentation.
  • 100plugin-development
    Create and run NetAlertX plugins. Use this when asked to create a plugin, run a plugin, test a plugin, or develop plugin functionality.
  • 95netalertx-plugin-run-development
    Create and run NetAlertX plugins. Use this when asked to create plugin, run plugin, test plugin, plugin development, or execute plugin script.
  • 100prettier-plugins
    Use when prettier plugins including plugin ecosystem, custom parsers, and plugin development.
  • 100neko-plugin
    Work on N.E.K.O plugins end to end. Use when the user asks to create, modify, review, run, debug, inspect, document, validate, package, or reason about N.E.K.O plugins, plugin.toml, plugin SDK usage, plugin UI surfaces, plugin CLI tooling, plugin runtime behavior, or plugin system contracts.
  • 90wp-plugin-development
    WordPress plugin architecture review for Codex. Use when reviewing plugin structure, lifecycle hooks, Settings API usage, CPT and taxonomy registration, hook design, i18n, and WordPress.org readiness.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.