skills

Unapprove Skill

Revoke content vetting: flip approved back to False (TOS-1492).

skills.approved is a catalog-level content-vetting flag, not a per-agent grant (per-agent visibility is artifact_approvals / LiveSetResolver, unaffected by this). Revoking it re-gates every surface that checks skills.approved (install eligibility, the live skill loader) for EVERYONE with access, not just the caller - that is the whole point of an "unapprove" action, so this uses the same edit+ rung as approve_skill (a content-editorial decision on the artifact within the folder, not a membership-management action - see services/access/rungs.py module docstring for the edit/admin distinction). A command-hook skill still requires re-approval by a platform admin (the approve_skill gate above); revoking that approval does not need the extra gate since revoking never grants anything.

post/api/skills/{skill_id}/unapprove

Request

  • Base URL: https://app.thinqos.com (the document declares no server; this is the origin it was published from)
  • URL: https://app.thinqos.com/api/skills/{skill_id}/unapprove
  • Auth: none declared

Path parameters

skill_idstring uuid required

Headers

x-impersonate-identity-idstring nullable

Response

Successful Response

idstring uuid required
slugstring required
library_idstring uuid nullable
library_namestring nullable
bundle_hashstring nullable
schema_versionstring required
versioninteger required
enabledboolean required
approvedboolean required
requires_admin_approvalboolean
visibility'private' | 'public' required
source_kind'authored' | 'imported' | 'bundled' | 'plugin' required
imported_fromstring nullable
import_status'installing' | 'failed' | 'ready'
import_errorstring nullable
bodystring required
tool_reachability_warningsstring[]
bundled_programsstring[]
import_warningsstring[]

Changes

No recorded changes to this operation across all 1 revision of this API.