human-signals 8.x

Use human-signals ^8.0.0 as an ES-module lookup table for signal metadata by name or number.

For

human-signals@8.0.1

Verified

2026-09-08, 2 examples executed

Package

@modootoday/pmcp-human-signals@8.0.0

What it covers

• What this package provides
• Look up a signal by name
• Look up a signal by number
• Platform support
• Version and compatibility pitfalls
• What this skill does not cover

One example from this skill

This is the skill's own text, not a summary of it. It runs: that is what verifying means here.

import assert from 'node:assert/strict'
import { signalsByName } from 'human-signals'

const sigint = signalsByName.SIGINT

assert.equal(sigint.name, 'SIGINT')
assert.equal(sigint.number, 2)
assert.equal(sigint.description, 'User interruption with CTRL-C')
assert.equal(sigint.supported, true)
assert.equal(sigint.action, 'terminate')
assert.equal(sigint.forced, false)
assert.equal(sigint.standard, 'ansi')

What it did in the sandbox

Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.

Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.

Getting it

With a subscription:

npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-human-signals

It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.