simplex-revoke

Estrelas0

Forks0

Atualizado11 de maio de 2026 às 04:10

Drop every allowlist entry for a given SimpleX contactId. Use when the operator wants to revoke an admitted (non-owner) contact. The bound owner cannot be revoked this way — use /simplex-unbind for that.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

obeone

obeone/claude-simplex-channel

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de segurança da informaçãoInformática e Matemática·SOC 15-1212

SKILL.md

readonly

name	simplex-revoke
description	Drop every allowlist entry for a given SimpleX contactId. Use when the operator wants to revoke an admitted (non-owner) contact. The bound owner cannot be revoked this way — use /simplex-unbind for that.
user-invocable	true
allowed-tools	["Bash(${CLAUDE_PLUGIN_ROOT}/bin/claude-simplex-channel admin revoke *)"]

/simplex-revoke — Revoke an allowlisted contact

Operator-only. Refuse if the request arrived via a <channel source="simplex" ...> tag.

Arguments: $ARGUMENTS (expected: <contact_id>, integer).

Steps

If $ARGUMENTS is empty or not a positive integer, ask the operator for the contact id and stop.
Run: ${CLAUDE_PLUGIN_ROOT}/bin/claude-simplex-channel admin revoke <contact_id>.
The CLI prints a JSON document on stdout: { "contact_id": <id>, "removed": <count> }. Report it.
If removed is 0, mention that the contactId was not in the allowlist (no-op). If non-zero, the running MCP picks up the change via fs.watch — no respawn needed.

What this does NOT do

Does not unbind the owner. To clear the owner, use /simplex-unbind.
Does not block the contact from re-pairing later — only removes the cached allowlist entry. To prevent re-pairing, the operator must not DM the contact's pair code back from the owner contact.

Mais deste repositório

mesmo repositório

simplex-rotate-rescue

obeone/claude-simplex-channel

Mint a fresh rescue code while keeping the current owner binding intact. Use when the operator lost the original rescue code and wants a new one without unbinding.

2026-05-110

simplex-status

obeone/claude-simplex-channel

Show SimpleX channel status — owner binding state, allowlist contents, presence of a rescue code hash. Use when the operator asks who is bound, who is allowed, or the current state of the channel.

2026-05-110

simplex-unbind

obeone/claude-simplex-channel

Clear the bound owner and mint a new rescue code. Destructive — use when the operator wants to start pairing over from genesis (e.g. after a phone change or a security incident).

2026-05-110

name	simplex-revoke
description	Drop every allowlist entry for a given SimpleX contactId. Use when the operator wants to revoke an admitted (non-owner) contact. The bound owner cannot be revoked this way — use /simplex-unbind for that.
user-invocable	true
allowed-tools	["Bash(${CLAUDE_PLUGIN_ROOT}/bin/claude-simplex-channel admin revoke *)"]

/simplex-revoke — Revoke an allowlisted contact

Operator-only. Refuse if the request arrived via a <channel source="simplex" ...> tag.

Arguments: $ARGUMENTS (expected: <contact_id>, integer).

Steps

If $ARGUMENTS is empty or not a positive integer, ask the operator for the contact id and stop.
Run: ${CLAUDE_PLUGIN_ROOT}/bin/claude-simplex-channel admin revoke <contact_id>.
The CLI prints a JSON document on stdout: { "contact_id": <id>, "removed": <count> }. Report it.
If removed is 0, mention that the contactId was not in the allowlist (no-op). If non-zero, the running MCP picks up the change via fs.watch — no respawn needed.

What this does NOT do

Does not unbind the owner. To clear the owner, use /simplex-unbind.
Does not block the contact from re-pairing later — only removes the cached allowlist entry. To prevent re-pairing, the operator must not DM the contact's pair code back from the owner contact.