api-identifier

Identify API interfaces from natural language requirements and query Apifox MCP documentation.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/liuwenji007/scpaiassests --skill api-identifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-identifier
Source: https://github.com/liuwenji007/scpaiassests/tree/main/.cursor/skills/api-identifier
Command: npx skills add https://github.com/liuwenji007/scpaiassests --skill api-identifier

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the identification of necessary API interfaces from natural language requirements and retrieves their detailed documentation, streamlining the API integration and development process.

Core Features & Use Cases

  • API Identification: Automatically recognizes API names from requirement descriptions.
  • Detailed Querying: Fetches comprehensive API information (path, method, parameters, responses) using a local Apifox MCP server.
  • Structured Output: Organizes retrieved API details into a structured format for workflow consumption.
  • Use Case: When a product manager describes a new feature, this Skill can automatically identify all the backend APIs needed to implement it and provide their documentation, saving developers significant lookup time.

Quick Start

Use the api-identifier skill to find APIs described in the following requirement: "I need to create a new user and retrieve a list of all users."

Frequently Asked Questions about api-identifier

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

FAQPage Schema
How do I identify required APIs from natural language requirements?

API identification from requirement descriptions involves parsing natural language text to recognize needed interface names and fetching their documentation. This Skill automates that process by querying a local Apifox MCP server for comprehensive API details.

How to query Apifox documentation automatically from business needs?

Querying Apifox documentation automatically involves mapping recognized API names from requirement texts to the local Apifox MCP server. This retrieves structured API information including paths, methods, parameters, and responses for workflow integration.

Can I fetch API path and method details from textual descriptions?

Yes, you can fetch API path and method details from textual descriptions. The Skill extracts API names from natural language requirements and retrieves comprehensive interface information, organizing path, method, and parameter data into a structured output format.

What is the best way to discover backend APIs for a new feature?

The best way to discover backend APIs for a new feature is using automated API identification from the product manager's requirement description. This approach recognizes necessary interfaces and provides their detailed documentation, saving developers significant manual lookup time.

Does API identification from requirements work with local Apifox MCP?

Yes, API identification from requirements works with a local Apifox MCP server. It leverages the server for detailed documentation retrieval, fetching comprehensive interface information like path, method, and parameters when processing natural language business needs.

What are the limitations of automatic API discovery from requirements?

Limitations of automatic API discovery include relying on a local Apifox MCP server for detailed documentation retrieval. If the required interfaces are not already documented in the local server, the Skill cannot fetch the comprehensive path, method, and parameter details.