AI Skill Report Card
Calling AICS OpenAPI
Quick Start12 / 15
Bashpython aics_openapi_tool.py --service_id "c514b8f3e73243d09a3919c49bbc54b1"
Recommendation▾
Remove verbose explanations like 'Navigate to Scripts Directory' - Claude knows how to use cd commands
Workflow10 / 15
-
Install Dependencies
Bashpip install requests -
Navigate to Scripts Directory
Bashcd .lingjiang/skills/aics_openapi/scripts -
Execute API Call
Bashpython aics_openapi_tool.py --service_id <SERVICE_ID> [OPTIONS]
Progress:
- Verify service ID is correct
- Prepare request body (if needed)
- Execute API call
- Validate response
Recommendation▾
Make examples more concrete by showing actual JSON response structures instead of just 'JSON response from AICS API displayed in console'
Examples12 / 20
Example 1: Basic Call
Input: python aics_openapi_tool.py --service_id "c514b8f3e73243d09a3919c49bbc54b1"
Output: JSON response from AICS API displayed in console
Example 2: Query with Body
Input: python aics_openapi_tool.py --service_id "c514b8f3e73243d09a3919c49bbc54b1" --body '{"query": "热值"}'
Output: Filtered results based on query parameter
Example 3: Save to File
Input: python aics_openapi_tool.py --service_id "abc123" --output result.json
Output: Response saved to result.json file
Recommendation▾
Consolidate the overly detailed parameter table and configuration section - these are basic concepts that don't need extensive explanation
Command Line Parameters
| Parameter | Required | Description | Example |
|---|---|---|---|
--service_id | Yes | AICS service identifier | c514b8f3e73243d09a3919c49bbc54b1 |
--body | No | POST request body (JSON string) | '{"input": {"key": "value"}}' |
--output | No | Output file path | result.json |
--verbose | No | Show detailed debug information | - |
Configuration
The tool uses resources/config.json:
JSON{ "api_config": { "base_url": "https://101.37.20.232/aics/api/openapi/invoke", "type": "EXPERIMENT" } }
Best Practices
- Always validate JSON format for
--bodyparameter - Use single quotes around JSON strings in command line
- Run from the scripts directory to ensure config file is found
- Use
--verbosefor debugging connection issues - Save important responses with
--outputparameter
Common Pitfalls
- Invalid JSON: Don't use malformed JSON in
--bodyparameter - Wrong Directory: Don't run from root directory; config.json won't be found
- Missing Service ID: Don't omit the required
--service_idparameter - Network Issues: Don't ignore SSL certificate errors; ensure HTTPS access to 101.37.20.232
- Character Encoding: Don't use non-UTF-8 characters without proper encoding