Skip to content
Nappai Documentation

ManagedSkill

The ManagedSkill component acts as a foundational building block within the NappAI ecosystem. Instead of performing a specific action itself, its primary role is to organize, label, and display other skills or automation tasks. It ensures that every skill in your workflow has a clear name, description, and visual icon, making your automation flows easier to read and manage. Think of it as the “profile” or “identity card” for a specific automation task, ensuring it is correctly identified by the system and the marketplace.

How it Works

This component does not execute any code or process data directly. Instead, it acts as a descriptor. When you use a skill in NappAI, this component provides the necessary metadata (such as the name, icon, and documentation link) that allows the system to recognize and display that skill correctly in your dashboard. It ensures consistency across all managed skills by defining the standard structure they must follow.

Inputs

The following fields are available to configure this component. Each field may be visible in different operations:

  • Name: A unique identifier or descriptive name for the skill (e.g., ‘slack’). This is typically set automatically by the system or marketplace to ensure the skill is correctly identified.

    • Visible in: All Operations

  • Description: A brief text explanation of what the skill does. This helps you and your team understand the purpose of the automation when viewing the dashboard.

    • Visible in: All Operations

  • Documentation: A link or path to the official documentation for the skill. This allows you to quickly access detailed guides or help resources for the specific automation.

    • Visible in: All Operations

  • Icon: The name of the icon to display in the user interface (e.g., “BookOpen”). This visual cue helps you quickly identify the type of skill in your workflow canvas.

    • Visible in: All Operations

Outputs

  • Skills: The component outputs a structured list or object containing the defined skills. This data is typically used internally by NappAI to populate the skill library or to be consumed by other components that need to reference or manage specific skills.

Output Data Example (JSON)json

{ “skills”: [ { “name”: “slack”, “description”: “A skill for interacting with Slack channels”, “icon”: “BookOpen”, “documentation”: “agents/skills/managed_skill” } ] }

Connectivity

This component is typically connected to other Management or Library nodes within NappAI. It serves as the source of truth for skill definitions, meaning its output can be mapped to components that need to display, list, or validate specific skills in your workflow. It does not usually connect to data-processing nodes like “Send Email” or “Read File” directly, but rather to nodes that manage the list or configuration of these skills.

Usage Example

Imagine you are building a workflow to manage integrations for your team. You can use the ManagedSkill component to define a new skill called “Slack Integration.” By setting the Name to “slack” and the Description to “Send messages to Slack,” you create a standardized entry in your library. Later, when you add a specific action node (like “Send Slack Message”), the system uses this managed skill definition to ensure the action knows which Slack account to use and how to display it in your dashboard.

Tips and Best Practices

  • Consistency is Key: Ensure that the Description field is clear and concise to help your team understand the skill’s purpose at a glance.
  • Use Standard Icons: Stick to standard icon names (like “BookOpen”) to maintain a clean and professional look in your NappAI dashboard.
  • Automatic Identification: Do not worry about manually changing the Name field unless necessary; the system often sets this automatically to ensure correct linking with other parts of the platform.

Security Considerations

  • Identity Verification: Since this component defines the identity of skills, ensure that the Name and Description match the official functionality of the skill to avoid confusion or misuse in your automation workflows.
  • Documentation Links: Verify that any Documentation links provided point to secure and authoritative sources to ensure your team accesses accurate information.