skills.rest
faisalanjum
faisalanjumCOMMUNITY
Explore all skills by this author →
GitHub

test-agent-field

Test agent field referencing for permissionMode and MCP tool access.

3|1|Updated Dec 2, 2024
Search Tags:#testing#security#permissions#agent#mcp#neo4j
One-click install
npx skills add https://github.com/faisalanjum/EventTrader --skill test-agent-field
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-agent-field
Source: https://github.com/faisalanjum/EventTrader/tree/main/.claude/skills/test-agent-field
Command: npx skills add https://github.com/faisalanjum/EventTrader --skill test-agent-field

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the need to verify if an agent's specified agent: field correctly grants the necessary permissions and tools for a given task, ensuring secure and intended agent interactions.

Core Features & Use Cases

  • Permission Verification: Tests if referencing an agent in the agent: field correctly assigns its permissionMode and tools to the skill.
  • Tool Accessibility Check: Confirms access to specific MCP tools required by the skill.
  • Use Case: Before deploying a skill that relies on another agent's capabilities (e.g., neo4j-report), this skill can be run to ensure the connection and permissions are set up as expected, preventing runtime errors.

Quick Start

Run the test-agent-field skill to check if the agent: neo4j-report field grants access to the mcp__neo4j-cypher__read_neo4j_cypher tool and allows query execution without permission prompts.

Frequently Asked Questions about test-agent-field

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

FAQPage Schema
How do I verify agent field permissions before deploying a skill?▼

To verify agent field permissions, run a test that checks if the agent field correctly assigns permissionMode and tool access. This validates MCP tool accessibility and executes a sample query to prevent runtime errors before deployment.

What does the permissionMode dontAsk setting do for agent fields?▼

The permissionMode dontAsk setting prevents unexpected permission prompts during agent interactions. Testing this ensures an agent executes queries and accesses MCP tools without interrupting the workflow with manual permission requests.

How do I test MCP tool accessibility for a specific agent?▼

Test MCP tool accessibility by referencing the target agent in the agent field and executing a sample query. This confirms whether the agent correctly grants access to required MCP tools like neo4j-cypher read operations.

Can I check if a neo4j-report agent has the right tool access before running it?▼

Yes, you can check neo4j-report agent tool access by testing the agent field configuration. This validates access to specific MCP tools like mcp__neo4j-cypher__read_neo4j_cypher and ensures query execution works without permission prompts.

Why does my agent field configuration trigger unexpected permission prompts?▼

Unexpected permission prompts occur when the permissionMode dontAsk setting is not correctly applied to the agent field. Running a permission verification test validates the configuration and identifies if tool access settings are improperly assigned.

Related Skills

Explore More Software Engineering Skills→
TheBushidoCollectiveTheBushidoCollective
187

claude-agent-sdk-tool-integration

Configure Claude Agent SDK tool permissions and MCP server access.

Official
Advanced
Harmitx7Harmitx7
3

config-validator

Validate internal references and file existence in the .agent directory.

Community
Intermediate
faisalanjumfaisalanjum
3

test-re-3layer-bot

Execute Cypher queries against a Neo4j graph database to retrieve company tickers.

Community
Basic
faisalanjumfaisalanjum
3

test-re-agent-field

Test the agent field in Skill definitions for direct tool access.

Community
Basic