graphify-full

Execute the full staged Graphify refresh workflow against raw inputs.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/pko89403/ZeroAlign-Rec --skill graphify-full
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphify-full
Source: https://github.com/pko89403/ZeroAlign-Rec/tree/main/.agents/skills/graphify-full
Command: npx skills add https://github.com/pko89403/ZeroAlign-Rec --skill graphify-full

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Alias wrapper for graphify-manager. Use when the user explicitly wants the full Graphify refresh workflow, not the code-only bootstrap refresh.

Core Features & Use Cases

  • Provides a repo-local entrypoint (/graphify-full) to trigger the complete staged refresh workflow using graphify-manager.
  • Standardizes the workflow to prevent partial or non-stage refresh paths and improve repeatability.

Quick Start

Run the graphify-full entrypoint to trigger the full refresh against raw/ using the graphify-manager workflow.

Frequently Asked Questions about graphify-full

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

FAQPage Schema
How do I run a full data-processing refresh workflow against raw inputs?

To run a full data-processing refresh workflow against raw inputs, execute the graphify-full entrypoint to trigger the complete staged producer path using the graphify-manager workflow, ensuring all stages process correctly.

When do I need a full staged producer path instead of a code-only bootstrap refresh?

You need a full staged producer path instead of a code-only bootstrap refresh when your scenario requires processing raw inputs through the complete end-to-end Graphify refresh workflow rather than just updating existing code structures.

What is the best way to standardize an automation workflow to prevent partial data-processing refreshes?

The best way to standardize an automation workflow to prevent partial data-processing refreshes is to use a repo-local entrypoint like graphify-full, which enforces the exact graphify-manager workflow and improves repeatability across runs.

Does the Graphify refresh workflow require a specific manager dependency to execute correctly?

The Graphify refresh workflow requires using the graphify-manager workflow exactly as specified, treating the skill as the repo-local /graphify-full entrypoint to ensure the staged producer path executes completely and correctly.

Can I trigger a complete staged refresh path directly from my repository?

Yes, you can trigger a complete staged refresh path directly from your repository by running the graphify-full entrypoint, which serves as the repo-local command to execute the full Graphify refresh workflow against your raw/ directory.

Why does my workflow require the graphify-manager instead of a standard bootstrap refresh?

Your workflow requires the graphify-manager instead of a standard bootstrap refresh because the full Graphify refresh workflow needs a completely staged producer path to process raw inputs, whereas a code-only bootstrap refresh skips these stages.