Community Skills Marketplace

Browse, install, and manage integration skills that give your agents new capabilities.

Overview

The Community Skills Marketplace is where you discover and install integration packages that give your agents new capabilities. Each skill defines a set of tools — like "create GitHub issue," "send Slack message," or "query Salesforce contacts" — that agents can use once the skill is installed and connected.

How Skills Work

Install — Adds the skill to your organization. No credentials needed yet.
Connect credentials — Add an API key, OAuth token, or bot token for the service.
Assign to agents — Enable the skill per-agent or org-wide from the agent's Skills tab.
Agent uses tools — The agent can now call the skill's tools during conversations.

Browsing Skills

The marketplace has four tabs:

Tab	Shows
Browse	All available skills, searchable and filterable
Installed	Skills you've installed — manage credentials, enable/disable, uninstall
Featured	Editor's picks and popular skills
Updates	Available updates for installed skills, update history

Filtering & Sorting

Search: Find skills by name or keyword
Category: Filter by category (development, communication, productivity, etc.)
Risk Level: Filter by risk assessment (low, medium, high, critical)
Sort: Newest, Most Popular, Highest Rated, or A–Z

Skill Cards

Each skill card shows:

Name, icon, and description
Number of tools provided
Category and risk level
Star rating and install count
Connection status (Connected / Not connected)
Verification badge (✓ Verified) for officially reviewed skills

Click any skill card to view full details including tool list, tags, reviews, and repository link.

Installing & Connecting

Install Flow

Click Connect on any skill card to open the credential setup modal. Depending on the skill's authentication type, you'll see different options:

OAuth 2.0 Skills

Two options (tabbed interface):

OAuth App (Recommended): Enter Client ID and Secret from the service's developer portal. The system handles the full OAuth flow with token refresh.
Access Token: Paste a Personal Access Token for quick setup. May have limited scopes.

For OAuth App setup, use this redirect URI in the service's developer portal:

https://your-domain.com/api/engine/oauth/callback

API Key / Token Skills

Paste the API key or token from the service's settings page. One field, encrypted with AES-256-GCM.

Multi-Field Credential Skills

Some services require multiple values (e.g., AWS Access Key ID + Secret Key). Each field is labeled and encrypted separately.

Credential Scopes

When connecting a skill, you choose the credential scope:

Scope	Behavior	Use When
Organization-wide	One set of credentials shared by all agents	Most cases — shared Slack bot, company GitHub token
Per-Agent	Each agent gets its own credentials	Different permission levels per agent (read-only vs. write)

All credentials are encrypted with AES-256-GCM and stored in the secure vault. They're never exposed in logs or the UI after saving.

Skill Updates

The Updates tab manages the lifecycle of installed skills.

Update Configuration

Setting	Options	Default
Auto-Update	Enabled / Disabled	Disabled
Check Interval	Hourly, Daily, Weekly, Manual Only	Daily
Max Risk Level	Low, Medium, High, Critical	Medium

When Max Risk Level is set to "Medium," auto-updates will only apply updates that don't increase risk above medium. Higher-risk updates require manual approval.

Managing Updates

Check for Updates: Manually scan for new versions of installed skills
Apply: Update a single skill to the latest version
Skip: Dismiss an update (it won't be shown again until a newer version is available)
Apply All: Update all skills at once

Each update shows the version change (e.g., v1.2 → v1.3), any risk level changes, and a changelog when available.

Update History

The update history table shows all past updates with skill name, version change, status (applied/failed/skipped), date, and who applied it.

Importing from GitHub

You can import custom skills from GitHub repositories:

Click Import from GitHub
Paste the repository URL
The system fetches the agenticmail-skill.json manifest
Review the manifest and click Publish

Important: Imported skills are stored in the database, not your codebase. They define tool schemas but need an MCP server or API endpoint to execute tools. Package updates don't affect imported skills.

Publishing Skills

To publish a skill to the marketplace, create a repository with an agenticmail-skill.json manifest that defines:

Skill metadata (name, description, author, version, category)
Tool definitions (name, description, input/output schemas)
Authentication requirements (OAuth, API key, etc.)
Risk assessment

Risk Levels

Each skill has a risk assessment that indicates its potential impact:

Level	Meaning	Examples
Low	Read-only access, no sensitive data	Weather API, public data queries
Medium	Write access to non-critical systems	Slack messaging, calendar events
High	Write access to critical systems	GitHub code changes, database writes
Critical	Can cause significant damage if misused	Payment processing, infrastructure changes

Best Practices

Start with verified skills — they've been reviewed for security and reliability
Review tools before installing — click on a skill to see exactly what tools it provides
Set conservative auto-update limits — use "Medium" max risk to prevent unexpected permission escalation
Use org-wide credentials unless you need per-agent permission differences
Check reviews — community ratings help identify well-maintained skills
Uninstall unused skills — fewer skills = smaller attack surface
Monitor the Updates tab — the yellow dot indicates available updates

Troubleshooting

Issue	Solution
Skill installed but tools not available	Credentials not configured. Click Connect on the skill in the Installed tab.
"Connected" but agent can't use tools	The skill may be disabled for that agent. Check the agent's Skills tab.
OAuth popup closes without connecting	Check browser popup blocker. Ensure redirect URI matches. Try the Access Token approach instead.
GitHub import fails	Verify the repository has an `agenticmail-skill.json` file at the root. The repo must be public or accessible.
Auto-update not working	Check Update Configuration — auto-update may be disabled or interval set to "Manual Only."
Skill shows "Update Available" dot	Go to the Updates tab to review and apply the update, or skip it.

Skills & Integrations — Manage installed skills and integrations catalog
Settings — Tool security and platform configuration
Guardrails — Control agent behavior with policies

AgenticMail Enterprise — Community Skills Marketplace Documentation

AgenticMail Enterprise Documentation Report an issue

Community Skills Marketplace

On This Page

Overview

How Skills Work

Browsing Skills

Filtering & Sorting

Skill Cards

Installing & Connecting

Install Flow

OAuth 2.0 Skills

API Key / Token Skills

Multi-Field Credential Skills

Credential Scopes

Skill Updates

Update Configuration

Managing Updates

Update History

Importing from GitHub

Publishing Skills

Risk Levels

Best Practices

Troubleshooting

Related Pages