con un clic
griptape-nodes-e2e
griptape-nodes-e2e contiene 6 skills recopiladas de griptape-ai, con cobertura ocupacional por repositorio y páginas de detalle dentro del sitio.
Skills en este repositorio
Confirm a Griptape Node's parameter configurations against a live engine via MCP tools, guided by a survey document from the griptape-nodes-e2e-survey skill. Produces a structured markdown inspection report with live-confirmed parameter details for each configuration. The output root directory must be provided in the task prompt.
Propose a complete test plan for a Griptape Node, driven by the inspection report and survey document. The plan is a self-contained test specification — the only input the workflow skill needs. It includes parameter-value configurations, error test sections, helper nodes, MCP constraints, and everything else required to generate test workflows. Supports both creating new plans and editing existing ones. The output root directory must be provided in the task prompt.
Given a node class name, locate its source code via MCP tools and analyse it to enumerate all parameter configurations — value-driven, connection-driven, and UI-message-driven. Produces a survey document that guides the inspect skill's live exploration. The output root directory must be provided in the task prompt.
Reference wiki for planning Griptape Nodes test workflows. Use when deciding which nodes to create, how to wire them, and which assertion nodes to use to validate outputs — i.e. the planning phase that precedes code generation. Do NOT use for writing pytest code (use the griptape-nodes-e2e-sdk skill for that).
End-to-end test generation pipeline for a Griptape Node. Orchestrates the survey, inspect, plan, and workflow skills in sequence. Confirms the output directory with the user, manages subagent execution, presents the test plan for approval, and gates workflow generation on that approval.
Build, validate, and save test workflows for a Griptape Node via MCP tools, driven by the test plan. The plan is the sole input — it contains configuration tests, error tests, helper nodes, MCP constraints, and everything else needed to generate workflows. Produces one saved workflow per testable section. The output root directory must be provided in the task prompt.