AF turingnet-iran-connectivity-engineer
Privacy-first, lawful connectivity troubleshooting for the Iran context (FA/EN) — use when diagnosing internet/service outages, Wi-Fi or mobile-data failures, DNS/TLS/cert problems, ISP last-mile issues, blackout continuity, or preparing redacted evidence, bilingual support tickets and low-bandwidth reports. Ships working scripts (PII redactor with Iranian formats + checksums, defensive guard, 60-second triage, status-page rate limiter, owned-scope diagnostics, ≤100KB report builder) and 55 templates. No bypass, no scanning, no credential collection — ever.
Privacy-first, lawful connectivity troubleshooting for the Iran context (FA/EN) — use when diagnosing internet/service outages, Wi-Fi or mobile-data failures…
As a process F 23/100 · Will not run — References files that are not bundled: templates/evidence_intake_bilingual.md, templates/home_network_playbook.md, templates/timeline.md
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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: templates/evidence_intake_bilingual.md - warning
missing-refreference to a missing file: templates/home_network_playbook.md - warning
missing-refreference to a missing file: templates/timeline.md - warning
missing-refreference to a missing file: templates/redacted_ticket_template.md - note
frontmatter-keyunknown frontmatter key "topics"
Process rating: all ten parameters 23/100
- 0Tools and files. 4 referenced file(s) missing: templates/evidence_intake_bilingual.md, templates/home_network_playbook.md, templates/timeline.md
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1494 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 563: enough signal without eating the budget
- +4Structure: 10 headings
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 7 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.