Skip to content

dongshuyan/compass-skills / skills/task-clarifier

task-clarifier

Verified

Deep need-clarification skill. Use only when the user explicitly invokes $task-clarifier. Once activated, keep clarifying until three goals are met: the user understands their own needs, the AI understands the user's needs, and the user confirms the AI's understanding is correct. Do not intervene in task execution unless explicitly invoked.

FileKindSize
SKILL.mdskill md15.8 KB
agents/openai.yamlconfig399 B
evals/test_behavior_guards.pyscript3.7 KB
evals/test_trigger_contract.pyscript839 B

evals/test_trigger_contract.py

View on GitHub
#!/usr/bin/env python3
"""Guard task-clarifier's explicit-invocation contract."""

from __future__ import annotations

from pathlib import Path
import re


SKILL_DIR = Path(__file__).resolve().parents[1]


def main() -> int:
    skill = (SKILL_DIR / "SKILL.md").read_text(encoding="utf-8")
    metadata = (SKILL_DIR / "agents" / "openai.yaml").read_text(encoding="utf-8")

    assert "$task-clarifier" in skill
    assert "trigger phrases" not in skill
    assert "policy:\n  allow_implicit_invocation: false" in metadata
    short_description = re.search(r'^  short_description: "(.*)"$', metadata, re.MULTILINE)
    assert short_description is not None
    assert 25 <= len(short_description.group(1)) <= 64

    print("ok=task-clarifier explicit trigger contract")
    return 0


if __name__ == "__main__":
    raise SystemExit(main())
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall