iblai-agent-setting

Configure mentor identity and actions in a Next.js Agent Settings tab.

15|3|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/iblai/vibe --skill iblai-agent-setting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iblai-agent-setting
Source: https://github.com/iblai/vibe/tree/main/skills/iblai-agent-setting
Command: npx skills add https://github.com/iblai/vibe --skill iblai-agent-setting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add a dedicated Agent Settings tab to configure mentor identity (name, description, avatar) and control visibility and actions like copy-to-tenant and delete within a Next.js app.

Core Features & Use Cases

  • Provides a reusable AgentSettingsProvider wrapper so multiple tabs (settings, llm, prompts, etc.) share identity and RBAC context.
  • Includes built-in modals for copying or deleting mentors and standardized branding guidelines.
  • Enables consistent agent configuration across tenants and teams in a Next.js project.

Quick Start

Wrap your agent route with AgentSettingsProvider and mount AgentSettingsTab to enable a fully functional Settings UI.

Frequently Asked Questions about iblai-agent-setting

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

FAQPage Schema
How do I add an agent settings tab to a Next.js app?

An agent settings tab in Next.js lets you configure mentor identity properties like name, description, and avatar, and control visibility alongside copy-to-tenant and delete actions within your app.

How do I share RBAC context across multiple agent settings tabs in Next.js?

You can share RBAC context across multiple agent settings tabs by wrapping the route with a single AgentSettingsProvider, allowing tabs like settings, llm, and prompts to share identity state.

Can I copy mentors to another tenant from within a Next.js application?

Yes, you can copy mentors to another tenant directly from the Next.js UI. The agent settings tab includes a built-in copy-to-tenant modal to facilitate this action across teams.

Do I need iblai tooling to configure agent visibility settings?

Yes, you need iblai tooling and environment setup to configure agent visibility settings. The integration requires wrapping routes with AgentSettingsProvider and following established brand guidelines.

What are the limitations of using a shared provider for agent settings?

The shared AgentSettingsProvider is limited to the Agent Settings family of tabs. It standardizes branding and identity sharing but requires strict adherence to iblai tooling and MCP workflow guidelines.