RobotForce.SystemActions 1.0.0

RobotForce.SystemActions

System-level action tiles for Robot Force workflows.

This module provides a set of reusable System Actions that allow workflows to interact with the operating system — reading/writing files, managing directories, listing contents, and executing commands.

Each action is exposed as a static tile definition and automatically generates its frontend configuration via InstructionConfig.

📦 Available Actions

1️⃣ ReadFile

Title: Read File
Description: Read text file into workflow variable

Reads the contents of a text file and makes it available inside the workflow.

Typical use cases:

• Load configuration files
• Read logs
• Import prompt templates
• Load intermediate workflow data

2️⃣ WriteFile

Title: Write File
Description: Write text content into a file (overwrite or append)

Writes text content into a file. Supports:

• Overwrite mode
• Append mode

Typical use cases:

• Save generated reports
• Export JSON results
• Persist agent output
• Create logs

3️⃣ EnsureDirectory

Title: Ensure Directory
Description: Create directory if it doesn't exist (mkdir -p)

Ensures a directory exists.
If it does not exist, it will be created.

Equivalent to:

mkdir -p path/to/directory

Typical use cases:

Prepare output folders

Ensure temp directories

Initialize workspace structure

4️⃣ ListDirectory

Title: List Directory
Description: List files in a directory (outputs JSON array)

Returns the contents of a directory as a JSON array.

Typical use cases:

Dynamic file processing

Batch workflows

File-based RAG ingestion

Folder scanning automation

Example output:

[
  "file1.txt",
  "file2.json",
  "subfolder"
]
5️⃣ RunCommand

Title: Run Command
Description: Run a process/command and capture stdout/stderr/exit code

Executes a system process and captures:

stdout

stderr

exit code

Typical use cases:

Call CLI tools

Execute scripts

Trigger builds

Run Python / Node scripts

Integrate external tools

🧠 Architecture

Each action:

Is implemented as a public static class

Defines:

description

title

category

Automatically generates frontend configuration via:

new InstructionConfig(...).result

The method reference is dynamically resolved using:

Type.GetType($"{Namespace}.Commands")
    .GetMethod(CurrentClassName)

This enables:

Automatic tile registration

Reflection-based binding

Consistent UI generation

Category-based grouping (ActionCategory.System)

🏗 Category

All actions are registered under:

ActionCategory.System

Meaning they are considered low-level system primitives inside Robot Force.

These tiles are typically used by:

AI agents

Automation workflows

File-processing pipelines

DevOps automations

Agentic process orchestration

🔐 Security Considerations

⚠ Since these actions operate on the system level:

File paths should be validated

Command execution should be sandboxed

Consider per-tenant isolation

Restrict execution permissions where needed

In production environments, these actions should run inside:

Isolated environments

VM workers

Sandboxed runtime contexts

🚀 Role in Agentic Automation

These system actions act as atomic building blocks for higher-level skills.

Example:

AI Agent → decides to generate report
→ EnsureDirectory
→ WriteFile
→ RunCommand (PDF converter)
→ ListDirectory
→ Return result

They are intentionally minimal and composable.

📌 Summary

RobotForce.SystemActions provides:

File I/O primitives

Directory management

Process execution

Structured frontend integration

Reflection-based tile registration