skills.rest
spencerbeggs
spencerbeggsCOMMUNITY
Explore all skills by this author →
GitHub

actions-inputs-outputs

Read GitHub Action inputs and write outputs using Effect schemas.

2|Updated Jul 2, 2026
Search Tags:#automation#schema#configuration#github-actions#ci-cd#effect
One-click install
npx skills add https://github.com/spencerbeggs/effected --skill actions-inputs-outputs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: actions-inputs-outputs
Source: https://github.com/spencerbeggs/effected/tree/main/plugin/skills/actions-inputs-outputs
Command: npx skills add https://github.com/spencerbeggs/effected --skill actions-inputs-outputs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the fragility of GitHub Action runner-file I/O by providing a type-safe, schema-backed interface that prevents silent failures, input mangling, and configuration drift.

Core Features & Use Cases

  • Typed Input Parsing: Safely read action inputs with automatic handling of GitHub's INPUT_ variable naming conventions and boolean/list/schema parsing.
  • Robust Output Management: Write outputs, summaries, and environment variables with built-in protection against runner-file corruption and encoding errors.
  • Contract Verification: Design and enforce machine-readable output contracts using Effect schemas to ensure downstream consumers receive stable, validated data.

Quick Start

Use the actions-inputs-outputs skill to define a schema-backed input reader and a validated output writer for your GitHub Action workflow.

Frequently Asked Questions about actions-inputs-outputs

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

FAQPage Schema
How do I parse GitHub Action inputs safely without configuration drift?▼

You can parse GitHub Action inputs safely by using type-safe Effect schemas that automatically handle the INPUT_ variable naming conventions and validate boolean, list, and schema data to prevent silent failures and input mangling.

What is the best way to enforce machine-readable output contracts in CI/CD?▼

Enforcing machine-readable output contracts in CI/CD is done by designing and applying Effect schemas to your workflow outputs, ensuring downstream consumers receive stable, validated, and structured data without runner-file corruption.

How do I write GitHub Actions environment variables and summaries without encoding errors?▼

You can write GitHub Actions environment variables and summaries without encoding errors by using a robust output management system that provides built-in protection against runner-file corruption during write operations.

Why does my GitHub Action configuration parsing fail silently during workflow execution?▼

GitHub Action configuration parsing fails silently when using fragile runner-file I/O without type-safe schemas, which causes input mangling and configuration drift due to unvalidated data and unhandled variable naming conventions.

Does this GitHub Action I/O approach work with Effect schemas for structured error handling?▼

Yes, this GitHub Action I/O approach works directly with Effect schemas to provide deterministic runner-file interaction, type-safe configuration parsing, and structured error handling for production-grade workflows.

Related Skills

Explore More Software Engineering Skills→
pagopapagopa
1

TechAICompositeAction

Create and modify GitHub composite actions with secure Bash scripting.

Official
Intermediate
pmcdowallpmcdowall

webhook-subscriptions

Create webhook subscriptions that trigger automated agent runs from external service events.

Community
Advanced
PaulJPhilpPaulJPhilp
785

effect-patterns-platform-getting-started

Standardize cross-platform Effect-TS operations for file I/O and environment access.

Community
Intermediate
AIDotNetAIDotNet
84

env-manager

Manage environment variables and .env files with validation, encryption, and template generation.

Official
Basic