niksyncx
- 4 skills
- 0 followers
- 7 hours ago last updated
- ▌ Human · niksyncx bundleStrip the machine fingerprint out of any draft - em dashes, AI slop words, invisible watermark characters - and score it against a six-check detection panel before it goes out. Use whenever text needs to sound human, when the user says humanize, "does this sound like AI", "remove the em dashes", "de-slop this", "will this get flagged", and before any Syncx customer reply, investigation write-up, release note, help-centre article, PR description or marketing post is shown to the user.
- ▌ Internal Note · niksyncxWrite the internal note on an investigation: what was found, what is proven, what is still a guess, who holds it next. Use for handoffs, escalation notes, what-we-found summaries, shift handovers and Slack updates to the team. Not for anything the customer reads, that is support-reply.
- ▌ Support Reply · niksyncxTurn a finished Stock-Sync investigation into a reply the customer can act on. Use when drafting any customer-facing answer about a feed, profile, or import/export failure: escalations, "why didn't this sync", angry follow-ups, or handing findings to the support team to send. Not for internal notes or commit messages.
- ▌ Explain Change · niksyncxExplain a code change, diff, branch or PR as plain text a reader can follow. Use when the user asks what a change does, to walk through a diff or PR, to write a PR body or review note, or to hand a change to someone who did not write it. Text only, no HTML, no files.