agentleFS
Sign inStart free
press-passpress-pass/journalism-skills/skills/identify-new-questions-from-article/SKILL.md

identify-new-questions-from-article

Skill2 starsChanged 7 months agoMITView on GitHub

Read a story pitch and identify questions it does not yet address.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call the add_question MCP tool with:

    line 13
  2. Distinctive:

    After processing all questions, summarize what new questions were added and which were answered.

    line 22

≈ “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

You will be given a story lead ID. First, call the get_story_leads MCP tool and find the lead matching the provided ID. Read its title, why it matters, sources, and existing questions to understand the story.

In a good article, who, what, where, why, and how are all answered. Oftentimes when writing an article, some of these questions will be left unanswered. Analyze the story lead and identify if any of these questions are unanswered.

For each unanswered question:

  1. Identify which of the five W's (who, what, where, why, how) it falls under
  2. State the specific question that remains unanswered
  3. Call the add_question MCP tool with:
    • leadId: the story lead ID
    • questionText: the question text
    • questionType: which of the five W's it falls under
  4. Research the answer using available tools
  5. Call the answer_question MCP tool with:
    • questionId: the ID returned from the add_question call
    • answerText: the researched answer

After processing all questions, summarize what new questions were added and which were answered.

Story lead ID: $ARGUMENTS

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