Skip to main content

manifold-api

Use when an agent needs to inspect or call the local Manifold HTTP API. Provides guidelines and scripts to filter specs before reading and handle payloads safely.

소스 정보

저장소
intelligencedev/manifold
최근 소스 활동
2026년 6월 4일 13:39
감지된 SKILL.md 언어
영어
스타
502
포크
31

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
2 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
manifold-api
description
Use when an agent needs to inspect or call the local Manifold HTTP API. Provides guidelines and scripts to filter specs before reading and handle payloads safely.
# Manifold API Skill ## Purpose The Manifold API skill is designed to interact safely with the local Manifold HTTP API running at `http:/localhost:32180`. It provides helper scripts to inspect the OpenAPI spec (`/openapi.json`) safely without dumping large documents into context, and rules for avoiding destructive operations and redacting sensitive information. ## Usage Use the provided shell script to interact with the Manifold API spec or health endpoints safely: ```bash # Check if the API is running ./manifold-api/main.sh healthz # Get the OpenAPI definition for a specific path (e.g., /api/projects) ./manifold-api/main.sh spec-path "/api/projects" ``` ## Configuration - **Dependencies**: `curl`, `jq` - **Target URL**: Defaults to `http:/localhost:32180` ## File Structure - `manifold-api/SKILL.md`: This documentation template and skill rules. - `manifold-api/main.sh`: Entry point script for interacting with the API safely. ## Best Practices & Rules 1. **Filter Specs**: Never dump the full `openapi.json` into context. Use the `main.sh spec-path` script to inspect one path at a time. 2. **Redaction**: Redact `apiKey`, bearer tokens, cookies, auth headers, and `extraHeaders` values in API responses. 3. **Safety First**: Always ask before modifying `/api/config/agentd` or deleting objects like specialists, teams, sessions, workflows, datasets, experiments, or prompt versions. 4. **Data Shapes**: Use live `GET` requests to discover the structure of `GenericObject` fields before sending `POST`/`PUT`/`PATCH` requests. Do not invent request fields.
GitHub에서 보기