/research-last-days
Research a topic from the past X days using web search. Specify the number of days or let it be inferred from your prompt.
$ npx -y skills add CoWork-OS/CoWork-OS --skill research-last-days --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/research-last-days
Context preview
The summary Claude sees to decide when to auto-load this skill.
Research a topic from the past X days using web search. Specify the number of days or let it be inferred from your prompt.
SKILL.md
research-last-days.SKILL.mdname: research-last-days
description: "Research a topic from the past X days using web search. Specify the number of days or let it be inferred from your prompt."
Last X Days Research
Purpose
Research a topic from the past X days using web search. Specify the number of days or let it be inferred from your prompt.
Routing
- Use when: Use when the user asks to research what happened recently on a topic, look up news from the last N days, or find recent trends and discussions.
- Do not use when: Do not use for planning documents, high-level strategy, or non-executable discussion.
- Outputs: Summary of recent findings with trends, patterns, and actionable insights.
- Success criteria: Returns concrete findings from the specified time period with sources and no fabricated results.
Trigger Examples
Positive
- Use the research-last-days skill for this request.
- Help me with last x days research.
- Use when the user asks to research what happened recently on a topic, look up news from the last N days, or find recent trends and discussions.
- Last X Days Research: provide an actionable result.
Negative
- Do not use for planning documents, high-level strategy, or non-executable discussion.
- Do not use research-last-days for unrelated requests.
- This request is outside last x days research scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | topic | string | Yes | The topic to research (e.g., 'AI agents', 'prompting techniques', 'Apple announcements') | | days | number | No | Number of days to look back (e.g., 1, 7, 14, 30, 90). Defaults to 7. | | tool | select | No | Target AI tool for the prompts (optional context) |
Runtime Prompt
- Current runtime prompt length: 1668 characters.
- Runtime prompt is defined directly in `../research-last-days.json`.
Read more
name: research-last-days description: "Research a topic from the past X days using web search. Specify the number of days or let it be inferred from your prompt."
Last X Days Research
Purpose
Research a topic from the past X days using web search. Specify the number of days or let it be inferred from your prompt.
Routing
- Use when: Use when the user asks to research what happened recently on a topic, look up news from the last N days, or find recent trends and discussions.
- Do not use when: Do not use for planning documents, high-level strategy, or non-executable discussion.
- Outputs: Summary of recent findings with trends, patterns, and actionable insights.
- Success criteria: Returns concrete findings from the specified time period with sources and no fabricated results.
Trigger Examples
Positive
- Use the research-last-days skill for this request.
- Help me with last x days research.
- Use when the user asks to research what happened recently on a topic, look up news from the last N days, or find recent trends and discussions.
- Last X Days Research: provide an actionable result.
Negative
- Do not use for planning documents, high-level strategy, or non-executable discussion.
- Do not use research-last-days for unrelated requests.
- This request is outside last x days research scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | topic | string | Yes | The topic to research (e.g., 'AI agents', 'prompting techniques', 'Apple announcements') | | days | number | No | Number of days to look back (e.g., 1, 7, 14, 30, 90). Defaults to 7. | | tool | select | No | Target AI tool for the prompts (optional context) |
Runtime Prompt
- Current runtime prompt length: 1668 characters.
- Runtime prompt is defined directly in `../research-last-days.json`.
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
- /attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide discovery passes with worker-specific threat models, semantically merge candidates, synthesize one canonical validation
Open skill - /finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /security-diff-scan
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
Open skill - /security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
Open skill