Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

casual-slack-tone

Sterne3

Forks1

Aktualisiert29. März 2026 um 18:09

Informal communication for Slack, chat, DMs, and quick check-ins. Conversational, first-person, correct punctuation but relaxed register. Use for Slack messages, informal reviews, and PR descriptions on own repos.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

robert-chiniquy

robert-chiniquy/dotfiles

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Sekretäre und Verwaltungsassistenten (außer Rechts-, Medizin- und Führungsbereich)Büro- und Verwaltungsberufe·SOC 43-6014

SKILL.md

readonly

name	casual-slack-tone
description	Informal communication for Slack, chat, DMs, and quick check-ins. Conversational, first-person, correct punctuation but relaxed register. Use for Slack messages, informal reviews, and PR descriptions on own repos.

Casual Slack Tone

For messages where formality would be weird.

Voice

First person, conversational
Correct punctuation and capitalization — not sloppy, just relaxed
Short sentences, short paragraphs
Contractions are fine
Direct and warm without being performative

Patterns

"hey, pushed a fix for the auth thing — was a stale token in the middleware"
"looked at this, the approach is solid. one thing: the timeout on L47 should probably match the retry interval"
"yeah that's a known issue, we worked around it in the SDK by..."

Anti-patterns

Corporate: "Per our discussion, I've actioned the deliverables"
Over-casual: "lol yea idk maybe fix it??"
Performative enthusiasm: "Love this approach! Super excited about..."

Mehr aus diesem Repository

gleiches Repository

authorization-model-review

robert-chiniquy/dotfiles

Reviewer persona for authorization models — RBAC, ABAC, ReBAC, and hybrids. Catches the bugs that ship after auth is correct but authz is wrong: missing tenant scoping, IDOR via predictable IDs, role escalation through unchecked write paths, permission caching staleness, transitive-trust loopholes, RBAC/ReBAC drift between policy doc and code. Use when reviewing endpoints that gate access by user/role/relationship, when adding a new role/permission/scope, when changing tenant isolation, or when designing a permission system from scratch. Triggers: RBAC, ABAC, ReBAC, IDOR, tenant isolation, multi-tenant, permission check, role, scope, principal, Zanzibar, OpenFGA, casbin, authz, can_, has_permission, isAuthorized.

2026-06-233

c1-dev-stack-in-squire

robert-chiniquy/dotfiles

Stand up a full c1 dev stack inside a Squire env — process-compose, postgres, envoy, pub-api, pub-auth, be-* services — wired so an external client can drive c1's gRPC surface end to end with TLS + OAuth2 client_credentials. Use when testing a Latchkey or other c1 client against a real (not stubbed) c1 backend, or when reproducing c1 server-side behavior locally. Triggers on: c1 dev env, squire c1 stack, pc/up, dev-util mint-test-client, test against c1, c1 OAuth client_credentials, run c1 integration tests in squire, repro buildkite integration test, TEST_LOCAL_EXEC, api_no_uplift.

2026-06-233

c1-squire-dispatch

robert-chiniquy/dotfiles

c1-specific values for the general squire dispatch protocols defined in squire-env-management. Provides the c1 gate bundle's contents, the task-family table for c1 work, the c1 always-actives, and the list of c1 skills that should NOT be spent on a squire env. Use when about to spawn a squire env to execute c1 work, when writing a brief for a remote c1 agent, or when filing a c1 bead intended for squire dispatch. Triggers: c1 squire dispatch, c1 squire brief, c1 remote work, c1 ephemeral env, c1 fire-and-forget.

2026-06-233

custom-crypto-detection

robert-chiniquy/dotfiles

Reviewer persona for detecting hand-rolled cryptography. Distinct from `sharp-edges` (which catches footgun APIs) and `key-lifecycle-review` (which covers lifecycle hygiene): this skill catches the class where someone wrote their own MAC, KDF, AEAD, signature scheme, secret-comparison routine, RNG, or password hash. Almost all custom crypto is broken. Use when reviewing any code that does math on bytes, manipulates buffers in a 'crypto-shaped' way, or implements something whose docs reference a named primitive (HMAC, AES-GCM, Argon2, X25519). Triggers: hand-rolled crypto, custom MAC, custom hash, custom KDF, byte XOR, constant-time compare, derived key, password hashing, HKDF, encrypt_then_mac, mac_then_encrypt, AE, AEAD.

2026-06-233

key-lifecycle-review

robert-chiniquy/dotfiles

Reviewer persona for the full lifecycle of cryptographic keys and high-value secrets: generation, storage, distribution, rotation, revocation, and destruction. Trail of Bits' `zeroize-audit` covers the destruction half; this skill covers the other four phases plus closes the loop with destruction. Use when reviewing key management code, secret stores, KMS integrations, rotation logic, key derivation, RNG usage, or any system that issues, holds, or revokes long-lived credentials. Triggers: key generation, key rotation, KMS, HSM, secret store, vault, key derivation, KDF, master key, DEK, KEK, rotation, revocation, RNG, entropy, random, secrets management.

2026-06-233

oauth-oidc-review

robert-chiniquy/dotfiles

Reviewer persona for OAuth 2.0 / 2.1 and OpenID Connect flow implementations. Catches the well-documented attack classes that still ship: missing PKCE, wildcard redirect URIs, mishandled refresh tokens, scope creep, mixed flows on a single endpoint, leaking tokens through referrer or logs, JWT signature bypass. Use when reviewing any code that issues, accepts, validates, exchanges, refreshes, revokes, or stores tokens; when designing a new auth integration; when a PR touches /authorize, /token, /userinfo, /jwks, /introspect, /revoke, OIDC discovery, or a third-party identity provider client. Triggers: OAuth, OIDC, JWT, PKCE, redirect_uri, scope, refresh token, access token, id_token, client_credentials, authorization code, implicit, device code, token exchange, identity provider, IdP, SSO.

2026-06-233

name	casual-slack-tone
description	Informal communication for Slack, chat, DMs, and quick check-ins. Conversational, first-person, correct punctuation but relaxed register. Use for Slack messages, informal reviews, and PR descriptions on own repos.

Casual Slack Tone

For messages where formality would be weird.

Voice

First person, conversational
Correct punctuation and capitalization — not sloppy, just relaxed
Short sentences, short paragraphs
Contractions are fine
Direct and warm without being performative

Patterns

"hey, pushed a fix for the auth thing — was a stale token in the middleware"
"looked at this, the approach is solid. one thing: the timeout on L47 should probably match the retry interval"
"yeah that's a known issue, we worked around it in the SDK by..."

Anti-patterns

Corporate: "Per our discussion, I've actioned the deliverables"
Over-casual: "lol yea idk maybe fix it??"
Performative enthusiasm: "Love this approach! Super excited about..."