nex

What This Skill Does

The Nex skill serves as an advanced interface for integrating your organizational context directly into the OpenClaw AI agent. It transforms the agent from a general-purpose model into a context-aware assistant by connecting it to your unique knowledge graph. With Nex, you can perform semantic queries across your stored notes, tasks, records, and relationships. The skill provides real-time access to your organizational data, allowing the AI to understand projects, stakeholders, and past discussions with high accuracy. It acts as a bridge, ensuring that your AI agent is not only intelligent but also deeply familiar with your specific business context.

Installation

To begin using the Nex skill, ensure you have an active account at https://app.nex.ai.

1. Obtain your API Key from the developer settings on the Nex dashboard.
2. Add the configuration to your ~/.openclaw/openclaw.json file as follows:

{
  "skills": {
    "entries": {
      "nex": {
        "enabled": true,
        "env": {
          "NEX_API_KEY": "sk-your_key_here"
        }
      }
    }
  }
}

3. Run the installation command: clawhub install openclaw/skills/skills/najmuzzaman-mohammad/nex.

Use Cases

• Project Management: Query current tasks and deadlines associated with specific team members to prepare for status meetings.
• Knowledge Retrieval: Quickly synthesize information about legacy documentation, onboarding materials, or past meeting notes to answer complex questions.
• Insight Generation: Stream live organizational insights directly into your workflow, allowing the agent to provide timely updates on evolving project states.

Example Prompts

1. "Nex, what are the current blockers identified in the Q3 marketing project according to our latest records?"
2. "Can you retrieve all notes related to the design meeting with John from last week and summarize the action items?"
3. "List all active tasks assigned to me in the 'Engineering' category and output them in a table format."

Tips & Limitations

• Latency: The Nex API frequently requires 10-60 seconds for processing. Always set a timeout: 120 in your exec tool calls to prevent premature termination.
• Security: The skill includes a rigorous nex-api.sh wrapper. Never manually concatenate user input into shell strings; rely on jq to build dynamic JSON bodies to prevent injection vulnerabilities.
• Output Handling: Responses can be quite large. Ensure that if your query returns over 10KB of data, your workflow includes logic to handle pagination or truncation. Use jq to filter only the fields you specifically need to keep token usage efficient.