Skip to content
Back to skills

Hayba Pcgex Node Selection

ASecurity

Use when choosing PCGEx nodes and pins for a specific graph operation, especially when documentation and installed plugin versions may differ.

  • 13 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 4, 2026
ai-agentsgonodedocumentation

Security analysis

A100/100

Scanned October 4, 2026

npx -y skills add zajalist/hayba --skill hayba-pcgex-node-selection --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Hayba Pcgex Node Selection?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Hayba Pcgex Node Selection
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/zajalist-hayba-pcgex-node-selection/badge)](https://www.skillsdirectory.com/skills/zajalist-hayba-pcgex-node-selection)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: hayba-pcgex-node-selection
description: Use when choosing PCGEx nodes and pins for a specific graph operation, especially when documentation and installed plugin versions may differ.
metadata:
  category: pcg
  tags: pcgex, nodes, pins, discovery
---

# Select PCGEx nodes from evidence

## When to use

Use when a graph needs a path, cluster, filter, scatter, or other specialized operation and the exact node class is uncertain. Describe the required input and output data before searching.

## Tool routing

- Search intent with `hayba_search_node_catalog`. `hayba_query_pcgex_docs` provides task-oriented documentation; `hayba_get_pattern_template` offers a starting topology. These are candidate sources, not proof of installed classes.
- Confirm a candidate with `hayba_get_node_details` and, in the target editor, `pcg_list_node_classes` plus `pcg_get_node_details`. Use `hayba_compatible_pins` to narrow downstream choices. If a graph already exists, inspect its actual dynamic pins with `pcg_list_pins`.
- Prefer native PCG when its simpler node covers the requirement. Record the PCGEx dependency when choosing a specialized node. Never guess a pin label from a screenshot or a different plugin version.

## Evidence

Return a small candidate table: class, intended role, observed pins, version/source confidence, and rejection reason for alternatives. Stop before mutation if the installed node or required pin cannot be confirmed; carry that as an explicit gap into hayba-pcg-build.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.