team
Use for team-knowledge sharing patterns — share captured patterns/decisions across teammates' SiftCoder installs, set up shared workspaces, federation hygiene.
What this skill does
# team Team knowledge sharing. Patterns + decisions cross human boundaries; SiftCoder federation is the mechanism. ## Surfaces - **Federation** — multiple workspaces share a memory cluster (already in the memory engine) - **Pattern publishing** — captured patterns can be tagged for team-visibility - **Decision broadcasting** — high-priority decisions auto-shared - **Privacy** — what stays local vs what shares ## Method 1. **Topology.** How many teammates, where do their installs live, do they share a memory backend? 2. **Federation setup.** - Single shared remote memory daemon? (centralised) - Per-user with periodic sync? (federated) 3. **Pattern visibility.** - `private` — only this user's installs - `team` — federation-shared - `public` — published to team registry 4. **Decision priority.** - Routine summaries — local - High-impact decisions — flagged for team broadcast 5. **Privacy.** PII never crosses workspace boundary; redaction enforced by `src/memory/privacy.ts`. ## Output shape ``` Team: <name> Members: <count> Federation: Mode: <central | federated> Backend: <URL or "local"; if federated, sync interval> Privacy: <PII redaction policy> Pattern visibility: Default: <private | team> Currently shared: <count patterns> Decision broadcast: Trigger: <priority threshold> Last broadcast: <timestamp + summary> Recommended actions: - <action — e.g. enable team federation> - <action> ``` ## Rules - **Privacy default-on.** PII redacted before any cross-workspace share. - **Federation opt-in.** Don't auto-federate. - **Decision broadcasts annotated.** "Team-shared" tag in memory for transparency. - **Local-first.** Local memory works without federation; federation enhances. ## Anti-patterns - Federation without redaction policy - Broadcasting routine summaries (noise) - Centralised memory without backup - Mixing prod team data with personal projects ## When NOT to use - Solo dev — federation is overhead - Heavily-regulated context — federation needs separate compliance review - Pre-onboarding — `/siftcoder:onboard` first ## Subagent dispatch - None for setup — uses memory CLI directly - Memory MCP for cross-workspace queries ## Value over native CC CC has no native team-memory federation. SiftCoder's memory engine supports it; this skill provides the operational discipline. The framework + privacy defaults are the value.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.