AF publisher
Publish HTML frontend projects to the PushWebly publishing platform, list published projects, obtain shareable project URLs, change a published app's public/private visibility, and package published HTML projects into Android APKs. Use when Codex needs to publish a local zip project, publish and build an APK, build an APK for an existing published project, toggle an app between public and private, list a user's published projects, or log in/register for this publishing platform. Codex should use HTTP APIs with curl when remote MCP tools are not mounted.
Publish HTML frontend projects to the PushWebly publishing platform, list published projects, obtain shareable project URLs, change a published app's…
As a process F 39/100 · Will not run — References files that are not bundled: URL
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: URL - note
edit-residuethe text marks something as outdated (lines 14): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 39/100
- 0Tools and files. 1 referenced file(s) missing: URL
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (publisher) differs from the folder (publisher-skills)
- 70Execution cost. Instruction body is 4131 tokens
- 85Steps. 43 steps, 2 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- high The skill tells the model to perform an irreversible action with no human approval
- low The response is described with custom markup (22 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 559: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 43 items
- +4Has examples (27 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.