{"id":"likaku-mck-ppt-design-skill","name":"Mck-ppt-design-skill","homepage":null,"repo_url":"https://github.com/likaku/Mck-ppt-design-skill","category":"devtools","subcategories":[],"tags":["powerpoint","pptx","python","design-system","slide-automation","charts","qa","python-pptx"],"what_it_does":"A Python-based PowerPoint (pptx) design system/engine that generates slide decks from high-level calls and a set of predefined layout patterns (including BLOCK_ARC chart rendering). It includes a post-generation QA pipeline with automated fixes to reduce overflow/collision/font consistency issues and performs PPT XML cleanup and CJK font handling.","use_cases":["Automatically generating consulting-style/pitch-deck PowerPoint slide decks from structured inputs","Creating and rendering chart-heavy decks with deterministic layout/geometry logic","Applying a consistent brand/typography/layout system across many slides","Auto-checking generated decks for text overflow, collisions, and legend/layout boundary issues"],"not_for":["Interactive/real-time presentation editing workflows","Using through a remote API without embedding the Python library","Production environments that require formal SLAs, documented operational error codes, or guaranteed backward compatibility without verification"],"best_when":"You want programmatic generation of .pptx files using Python (python-pptx) with consistent, repeatable layouts and automatic QA/fix-up of common rendering defects.","avoid_when":"You need a network service with REST/GraphQL endpoints, OAuth, webhooks, or strong guarantees of stable behavior across versions without running tests.","alternatives":["python-pptx with your own layout templates","commercial slide automation/tools that provide template-based PPT generation","in-house templating engines that render to PPTX using prebuilt masters/layouts"],"af_score":59.2,"security_score":39.5,"reliability_score":35.0,"package_type":"skill","discovery_source":["openclaw"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:55:38.138131+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":true,"sdk_languages":["Python"],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"No authentication described; this appears to be a local/offline Python library that writes .pptx files."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided in the supplied README excerpt; license is Apache-2.0."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":59.2,"security_score":39.5,"reliability_score":35.0,"mcp_server_quality":0.0,"documentation_accuracy":45.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":100.0,"rate_limit_clarity":0.0,"tls_enforcement":0.0,"auth_strength":70.0,"scope_granularity":0.0,"dependency_hygiene":40.0,"secret_handling":80.0,"security_notes":"No remote service is described, so TLS/auth around network transport are not applicable. As a local PPT generator, risk is mainly around handling font assets and any external resources; the excerpt emphasizes deterministic cleanup (_clean_shape/full_cleanup) which can reduce corrupted output but does not address supply-chain dependency scanning or runtime sandboxing. No secret handling details are provided; assume typical library usage without credentials.","uptime_documented":0.0,"version_stability":40.0,"breaking_changes_history":30.0,"error_recovery":70.0,"idempotency_support":"false","idempotency_notes":"Library behavior is not described as idempotent; repeated runs may regenerate or overwrite PPTX output files.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["No network interface or agent-friendly contract (MCP/REST) is documented; agents must use the Python API surface.","If QA/autofix fails to reach a 0-error gate, the run behavior/returned artifact is not fully specified in the excerpt—agents should be prepared to handle failures after save and/or during autofix."]}}