Skip to content

aiskillstore/marketplace / skills/0xsero/api-skill

api-skill

Verified

Updated API skill

FileKindSize
SKILL.mdskill md79 B
skill-report.jsonconfig7.4 KB

skill-report.json

View on GitHub
{
  "schema_version": "2.0",
  "meta": {
    "generated_at": "2026-07-04T14:20:30.374Z",
    "slug": "0xsero-api-skill",
    "source_url": "https://github.com/0xSero/orchestra/tree/main/examples/orchestra/.opencode/skill/api-skill",
    "source_ref": "main",
    "model": "codex",
    "analysis_version": "3.0.0",
    "source_type": "community",
    "content_hash": "c5d9ca54786d0257cc9e412f3dc1f600aaef415d79ef1a914afe23062ae818f5",
    "tree_hash": "e0508a50b6ad682d76f08c98157b7d133193e3b09deca2e42d5591306dbd902e",
    "provenance": {
      "model_effective": "codex",
      "fallback_chain": [
        {
          "agent": "codex",
          "outcome": "success"
        }
      ],
      "analysis_version": "3.0.0"
    }
  },
  "skill": {
    "name": "api-skill",
    "description": "Minimal prompt-only skill for API-related tasks and API prompt drafting.",
    "summary": "Gives AI coding assistants a lightweight API-focused prompt context.",
    "icon": "📦",
    "version": "1.0.1",
    "author": "0xSero",
    "license": "MIT",
    "category": "coding",
    "tags": [
      "api",
      "prompts",
      "coding",
      "api-design",
      "developer-workflow"
    ],
    "supported_tools": [
      "claude",
      "codex",
      "claude-code"
    ],
    "risk_factors": []
  },
  "security_audit": {
    "risk_level": "safe",
    "is_blocked": false,
    "safe_to_publish": true,
    "analysis_status": "ok",
    "summary": "Static analysis reported no suspicious patterns in the single prompt-only file. Manual review found only front matter and a short API prompt, with no prompt injection attempt or executable behavior.",
    "remediation": [],
    "risk_factor_evidence": [],
    "static_findings": [],
    "finding_verdicts": [],
    "semantic_findings": [],
    "critical_findings": [],
    "high_findings": [],
    "medium_findings": [],
    "low_findings": [],
    "dangerous_patterns": [],
    "files_scanned": 1,
    "total_lines": 8,
    "audit_model": "codex",
    "audited_at": "2026-07-04T14:20:30.374Z",
    "agent_auto_install_policy": "allowed",
    "manual_install_policy": "allowed"
  },
  "content": {
    "user_title": "Draft API prompts faster",
    "value_statement": "API work often starts with vague prompts and uneven requirements. This skill gives Claude, Codex, and Claude Code a minimal API-focused starting point.",
    "seo_keywords": [
      "Claude",
      "Codex",
      "Claude Code",
      "API skill",
      "API prompt",
      "API design assistant",
      "developer workflow",
      "endpoint planning",
      "prompt-only skill"
    ],
    "actual_capabilities": [
      "Frames requests around API-related work using a minimal prompt stub.",
      "Runs as a prompt-only skill with no included scripts or tools.",
      "Uses the skill metadata name api-skill for discovery.",
      "Allows the host assistant to choose the model through model: auto.",
      "Can guide API-related conversations when the user supplies project details."
    ],
    "limitations": [
      "The skill does not include API templates, schemas, or framework-specific guidance.",
      "It cannot inspect services or endpoints unless the user provides those materials.",
      "It does not execute tests, make network calls, or validate live APIs.",
      "The prompt content is very brief, so results depend heavily on user instructions."
    ],
    "use_cases": [
      {
        "title": "Plan a new endpoint",
        "description": "Product engineers can turn a rough endpoint idea into clearer request, response, and error requirements.",
        "target_user": "Backend engineer"
      },
      {
        "title": "Review API task wording",
        "description": "Technical leads can tighten API implementation prompts before assigning work to an AI coding assistant.",
        "target_user": "Technical lead"
      },
      {
        "title": "Prepare API documentation tasks",
        "description": "Documentation writers can structure prompts for endpoint summaries, parameter notes, and usage guidance.",
        "target_user": "Documentation writer"
      }
    ],
    "prompt_templates": [
      {
        "title": "Clarify an API task",
        "prompt": "Summarize the API task for [feature]. List the endpoint goal, required inputs, expected output, and open questions.",
        "scenario": "Beginner prompt for turning a rough idea into a clear API task."
      },
      {
        "title": "Draft an endpoint prompt",
        "prompt": "Create a concise implementation prompt for an API endpoint that supports [workflow]. Include authentication assumptions, validation rules, and error cases.",
        "scenario": "Intermediate prompt for preparing work for an AI coding assistant."
      },
      {
        "title": "Review an API brief",
        "prompt": "Review this API design brief for missing requirements: [brief]. Identify unclear fields, edge cases, security concerns, and test scenarios.",
        "scenario": "Advanced prompt for improving API requirements before implementation."
      },
      {
        "title": "Plan a service change",
        "prompt": "Transform this multi-service API change into an execution plan: [context]. Separate contract changes, migration risks, backward compatibility, observability, and rollout checks.",
        "scenario": "Advanced prompt for coordinating broader API changes."
      }
    ],
    "output_examples": [
      {
        "input": "A user asks for a prompt to build a user settings endpoint.",
        "output": "The assistant returns a structured API task brief with purpose, inputs, response expectations, validation, permissions, and open questions."
      },
      {
        "input": "A user provides an API design brief with missing details.",
        "output": "The assistant highlights missing authentication rules, unclear error handling, ambiguous fields, and test scenarios to confirm."
      }
    ],
    "best_practices": [
      "Provide endpoint purpose, user role, data shape, and failure cases before asking for output.",
      "Ask for assumptions and open questions when API requirements are incomplete.",
      "Pair generated API prompts with human review before implementation."
    ],
    "anti_patterns": [
      "Do not expect the skill to infer private service behavior without context.",
      "Do not treat generated API text as a tested contract.",
      "Do not include secrets, tokens, or production credentials in prompts."
    ],
    "faq": [
      {
        "question": "Does this skill run code?",
        "answer": "No. It is a prompt-only skill and does not include scripts or executable tooling."
      },
      {
        "question": "Can it call my API?",
        "answer": "No. It does not include network tooling or live endpoint validation."
      },
      {
        "question": "What should I provide?",
        "answer": "Describe endpoint goals, consumers, authentication, inputs, outputs, and constraints."
      },
      {
        "question": "Does it replace API review?",
        "answer": "No. Use it to prepare prompts, then review generated API plans before implementation."
      },
      {
        "question": "Which tools are supported?",
        "answer": "The report lists support for Claude, Codex, and Claude Code."
      },
      {
        "question": "Was malicious behavior found?",
        "answer": "No evidence of malicious behavior was found in the reviewed prompt-only file."
      }
    ]
  },
  "file_structure": [
    {
      "name": "SKILL.md",
      "type": "file",
      "path": "SKILL.md",
      "lines": 8
    }
  ]
}
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall