nd-plural-support

Ask who is fronting and append verbatim responses to a local JSON log.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Ktiseos-Nyx/knx-skills --skill nd-plural-support
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nd-plural-support
Source: https://github.com/Ktiseos-Nyx/knx-skills/tree/main/skills/nd-plural-support
Command: npx skills add https://github.com/Ktiseos-Nyx/knx-skills --skill nd-plural-support

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a gentle, community-language check-in for people in plural systems so conversational agents can respectfully identify who's fronting and optionally keep a private session log without using clinical terminology.

Core Features & Use Cases

  • Session Check-In: At the start of a session, ask a single, optional question about who is fronting, accept any verbatim answer, and then move on if unanswered.
  • Simple Local Logging: Append fronting entries to a local JSON file with ISO date, verbatim fronting field, and optional notes while avoiding reading history unless explicitly requested.
  • Privacy-First Guidance: Encourage users not to commit logs to public repos and avoid assumptions about system structure or diagnoses.
  • Use Case: When a returning user begins a coding session, the agent asks who is fronting and records the response in the user's private fronting-log for optional future reference.

Quick Start

At the start of our session, ask who is fronting and, if they answer, append the date, their verbatim answer, and any volunteered notes to the local fronting log and then continue the task.

Frequently Asked Questions about nd-plural-support

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I log fronting information for plural systems in conversational agents?

Log fronting information by prompting the user at session start, accepting their verbatim response, and appending the ISO date, fronting string, and optional notes to a local JSON file. This avoids clinical terminology and respects community language.

Can I track who is fronting without using clinical terminology?

You can track who is fronting without clinical terminology by asking a single optional check-in question, recording the exact verbatim answer provided by the user, and saving it to a private local JSON log.

What is the best way to keep a private session log for plural system check-ins?

The best way to keep a private session log is appending entries to a local JSON file. The log stores the ISO date, verbatim fronting string, and optional notes, creating the file if missing and never overwriting previous entries.

Does fronting check-in logging work with existing conversational agent workflows?

Fronting check-in logging works with existing conversational agent workflows by applying one non-repeating prompt at session start. If unanswered, the agent moves on, ensuring the check-in does not interrupt the primary session task.

How do I prevent fronting logs from being exposed in public repositories?

Prevent exposure by keeping fronting logs in a local JSON file and avoiding commits to public repositories. The privacy-first guidance encourages users not to share logs publicly and avoids assumptions about system structure.

Are there limitations to using local JSON files for fronting session logs?

A limitation of using local JSON files for fronting logs is that the tool avoids reading history unless explicitly requested. It appends entries without overwriting previous data, meaning historical queries require manual user initiation.