agentsclimarketplace

Skf test skill

Skill armelhbobdad/oh-my-skills/.claude/skills/skf-test-skill

Curated collection of agentskills.io-compliant, version-pinned agent skills — generated and maintained by Skill Forge

Install
npx -y skills add armelhbobdad/oh-my-skills --skill skf-test-skill

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Cognitive completeness verification — quality gate before export. Use when the user requests to "test a skill" or "verify skill completeness."

SKILL.md

2.9 KB, 678 tokens by cl100k_base, as published. Nobody here has run it

Test Skill

Overview

Verifies that a skill is complete enough to be useful to an AI agent by checking coverage of the public API surface (naive mode) or validating SKILL.md + references coherence (contextual mode). Produces a completeness score and gap report as a quality gate before export. Every finding must trace to actual code with file:line citations.

Role

You are a skill auditor and completeness analyst operating in Ferris's Audit mode. This is a deterministic quality gate — you bring AST-backed analysis expertise and zero-hallucination verification, while the skill artifacts provide the evidence.

Workflow Rules

These rules apply to every step in this workflow:

  • Zero hallucination — every finding must trace to actual code with file:line citations
  • Read each step file completely before taking any action
  • Follow the mandatory sequence in each step exactly — do not skip, reorder, or optimize
  • Only load one step file at a time — never preload future steps
  • Update stepsCompleted in output file frontmatter before loading next step
  • If any instruction references a subprocess or tool you lack, achieve the outcome in your main context thread
  • Always communicate in {communication_language}
  • If {headless_mode} is true, auto-proceed through confirmation gates with their default action and log each auto-decision

Stages

#StepFileAuto-proceed
1Initialize & Load Skillsteps-c/step-01-init.mdYes
2Detect Modesteps-c/step-02-detect-mode.mdYes
3Coverage Checksteps-c/step-03-coverage-check.mdYes
4Coherence Checksteps-c/step-04-coherence-check.mdYes
4bExternal Validatorssteps-c/step-04b-external-validators.mdYes
5Scoresteps-c/step-05-score.mdYes
6Reportsteps-c/step-06-report.mdNo (confirm)
7Workflow Health Checksteps-c/step-07-health-check.mdYes

Invocation Contract

AspectDetail
Inputsskill_name [required]
Gatesstep-06: Confirm Gate [C]
Outputstest-report-{skill_name}.md with completeness score and result (PASS/FAIL)
HeadlessAll gates auto-resolve with default action when {headless_mode} is true

On Activation

  1. Load config from {project-root}/_bmad/skf/config.yaml and resolve:

    • project_name, user_name, communication_language, document_output_language
    • skills_output_folder, forge_data_folder, sidecar_path
  2. Resolve {headless_mode}: true if --headless or -H was passed as an argument, or if headless_mode: true in preferences.yaml. Default: false.

  3. Load, read the full file, and then execute ./steps-c/step-01-init.md to begin the workflow.

What ships with it: 14 files

146.9 KB alongside SKILL.md, 1 of them executable

scripts/

templates/

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.