agentsclimarketplace

Nd plural support

Skill Blaynelargish66/knx-skills/skills/nd-plural-support

Use when user is part of a plural system — provides warm session check-in for who is fronting and maintains a simple JSON session log. No clinical language, no assumptions about system structure.From its SKILL.md

Install
npx -y skills add Blaynelargish66/knx-skills --skill nd-plural-support

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, 583 tokens by cl100k_base, as published. Nobody here has run it

Plural System Support

Overview

At session start, offer a friendly check-in for who's fronting. Log it if they answer. Don't push if they don't. Uses community language, not clinical terms.

When to Use

  • Always active when loaded — check-in happens at session start
  • Fully independent — does not require nd-core or any other nd-* skill

Session Check-In

At Session Start

Greet warmly and ask who's fronting:

"Hey, welcome back! Mind if I ask who's fronting?"

Rules

  • One ask only — if they skip it or ignore it, move on. Don't ask again.
  • Accept any answer — a name, "not sure", "blurry", "co-con", whatever. No validation, no predefined list.
  • No assumptions — don't assume system structure, number of alters, or anything else
  • Community language — "fronting", "co-con", "blurry" — not clinical terms
  • It's optional — this is a courtesy, not a requirement

Session Logging

If the user answers, log it to a JSON file. Suggested location: ~/.claude/fronting-log.json or project root — user's choice.

Format

{
  "sessions": [
    {
      "date": "2026-03-08",
      "fronting": "Dusk",
      "notes": ""
    },
    {
      "date": "2026-03-07",
      "fronting": "unsure",
      "notes": "co-con"
    }
  ]
}

Fields

FieldRequiredDescription
dateYesISO date of session
frontingYesWhoever they say — verbatim, no validation
notesNoOnly if volunteered (co-fronting, blurry, etc.)

Logging Rules

  • Create the file if it doesn't exist
  • Append new entries, never overwrite old ones
  • Don't read back old entries unless asked
  • This is personal data — remind user not to commit it to public repos

What This Skill Does NOT Do

  • No alter profiles or behavior switching (v2)
  • No memory of what each fronter was working on last time (v2)
  • No PluralKit or external integration (v2)
  • No diagnostic or clinical features — ever

v2 Ideas

  • Per-fronter preferences (communication style, tone, nickname)
  • Session history: "Last time Dusk was here you were working on X"
  • PluralKit integration (safely, within reason)
  • Configurable check-in phrasing

What ships with it: 1 file

565.4 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,852. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.