agentleFS
Sign inStart free
yogsoth-aiyogsoth-ai/de-anthropocentric-research-engine/skills/apply-question-framework/SKILL.md

apply-question-framework

Skill505 starsChanged 48 days agoApache-2.0View on GitHub

Select and instantiate a research-question schema appropriate to study type.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every populated field traces to the input question or context.

    line 36
  2. Distinctive:

    Do not force a causal question into a descriptive framework or fill absent fields from convention.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

apply-question-framework

Purpose

Structure an underspecified research question with a declared question framework.

Input contract

required: [question, research_context, framework]
optional: [population, intervention, comparator, outcome, time_horizon]
constraints: [framework fields must be instantiated or marked unknown]

Procedure

  1. Select the framework matching the question type.
  2. Map the question into its required fields.
  3. Mark missing, ambiguous, and non-applicable fields.
  4. Emit the structured question and scope decisions.

Output contract

produces: [structured_question, field_map, missing_fields, scope_decisions]
delta_fields: [findings, decisions, uncertainties, open_questions]

Quality gates

  • Every populated field traces to the input question or context.
  • Framework choice is justified.

Failure and counterexamples

Do not force a causal question into a descriptive framework or fill absent fields from convention.

Provenance map

  • resolved: apply-question-framework

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free