radicle
This skill should be used when the user asks to "initialize a radicle repo", "rad init", "create a patch", "open a patch", "rad patch", "clone from radicle", "rad clone", "work with radicle issues", "rad issue", "start radicle node", "rad node", "seed a repository", "sync with radicle", "push to radicle", "collaborate on radicle", or mentions RIDs, DIDs, patches, seeding, or peer-to-peer code collaboration.
What this skill does
# Radicle Radicle is a decentralized, peer-to-peer code collaboration protocol built on Git. It enables sovereign code hosting using cryptographic identities and a gossip-based network. ## Core Concepts - **RID** (Repository ID): Globally unique URN, e.g. `rad:z31hE1wco9132nedN3mm5qJjyotna` - **NID** (Node ID): Device identifier on the network - **DID** (Decentralized Identifier): Self-sovereign identity, e.g. `did:key:z6Mkhp7VU...` - **Delegates**: Maintainers who can sign and manage repository metadata - **Seeding**: Hosting/replicating a repository across the network - **Patches**: Git-based collaborative objects (like pull requests) with revision history ## Quick Reference | Task | Command | |------|---------| | Check identity | `rad self` | | Current repo RID | `rad .` | | Node status | `rad node status` | | Initialize repo | `rad init --name "name" --description "desc" --public --no-confirm` | | Clone | `rad clone rad:<RID>` | | Create patch | `git push rad HEAD:refs/patches` (set description with `rad patch edit`) | | Update patch | `git push --force` (on patch branch) | | List patches | `rad patch list` (also `--all`/`--merged`/`--draft`/`--archived`) | | Show patch | `rad patch show <PATCH_ID>` (`--patch` to include diff) | | Checkout patch | `rad patch checkout <PATCH_ID>` | | Review patch | `rad patch review <PATCH_ID> --accept` / `--reject` | | Merge patch | `git checkout main && git merge <branch> && git push rad main` | | List issues | `rad issue list` (also `--all`/`--closed`/`--solved`/`--assigned`) | | Open issue | `rad issue open --title "title" --description "desc" --labels "bug ux"` | | Show issue | `rad issue show <ISSUE_ID>` | | Comment on issue | `rad issue comment <ISSUE_ID> --message "text"` | | Close issue | `rad issue state <ISSUE_ID> --closed` (also `--open`/`--solved`) | | Label issue | `rad issue label <ISSUE_ID> --add <label>` / `--delete <label>` | | Start node | `rad node start` | | Sync | `rad sync --announce` | | Fetch updates | `rad sync --fetch` | | Add remote | `rad remote add <NID> --name <alias>` | | Seed repo | `rad seed rad:<RID>` | ## Multiline text (heredoc) Prose flags (`--description`, `--message`, `-m`, `--title`) take multiline values via a quoted heredoc — no editor needed. Quote the delimiter (`'EOF'`) so `$` and backticks stay literal: ```bash rad issue open --title "Title" --labels discussion --description "$(cat <<'EOF' First paragraph. - point one EOF )" ``` Patches are the exception: a patch's title/description can't ride on a `git push` option (those reject newlines). Push to open the patch, then set the description with `rad patch edit` — its `-m` is an ordinary arg, so the heredoc works (first line = title, rest = body): ```bash git push rad HEAD:refs/patches # opens the patch rad patch edit <PATCH_ID> -m "$(cat <<'EOF' Patch title Body, independent of the commit message. EOF )" ``` Same `-m "$(heredoc)"` works for `rad patch update`/`comment` and `rad patch review -m`. For the commit-message-as-description alternative, see `references/commands.md`. ## Flag gotchas The real flags, so you don't guess or fall back to `--help`: - List filters are boolean flags, not `--state`: `rad issue list --closed`, `rad patch list --merged`. - Add/remove is `--add`/`--delete` (not `--remove`) for `issue label`, `issue assign`, `patch label`, `patch assign`. - `rad issue open` takes `--labels` and `--assignees` (space-separated) at creation time. - `rad patch comment` takes a REVISION_ID, not a patch ID. `references/commands.md` has the full verified flag list — read it instead of running `rad <cmd> --help`. ## Key Workflows ### Contribute to a Project 1. `rad clone rad:<RID>` 2. `git checkout -b feature-branch` 3. Make changes, commit 4. `git push rad HEAD:refs/patches` 5. Address feedback: `git push --force` ### Review and Merge 1. `rad patch list` to see open patches 2. `rad patch show <ID>` or `rad patch checkout <ID>` 3. `git checkout main && git merge <branch>` 4. `git push rad main` (marks patch as merged) ### Private Repository 1. `rad init --private` 2. `rad id update --allow <DID>` to grant access 3. `rad id update --disallow <DID>` to revoke ### Mirror to GitHub If the repo has a GitHub remote, push to both: `git push rad main && git push github main`. See `references/github-mirror.md` for automation setup. ## Troubleshooting **Node not running**: Run `rad node start`, then `rad node status` to verify. **Sync issues**: Run `rad sync --fetch` then `rad sync status`. **Identity problems**: Run `rad self` to check, `rad auth` to re-authenticate. **Node status symbols**: `✓` connected, `!` attempted, `✗` disconnected, `↗` outbound, `↘` inbound. **NAT/firewall**: "Not configured to listen for inbound connections" is normal. The node still connects outbound and participates fully. Configure port forwarding for inbound. ## Prerequisites ```bash rad --version # Check installation rad self # Check identity rad node status # Check node ``` If `rad` is not installed: https://radicle.xyz/install or `curl -sSLf https://radicle.xyz/install | sh` If no identity: `rad auth` (or non-interactive: `echo "" | rad auth --alias "name" --stdin`)
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.