Index of every page on this site: llms.txt
All skills
nimrodfisher avatar

/analysis-planning

@9449d36
Run it yourself

Structure analysis approach before starting work. Use when receiving new analysis requests, breaking down complex questions into steps, or planning iterative analysis workflows.

Use this Skill: https://skilld.dev/gh/nimrodfisher/data-analytics-skills/analysis-planning

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈49 tokens for metadata: the name and description. ≈422 when used: this file. ≈3.4k more on demand in 5 files.

Description uses 2.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈197 characters, or 2.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

When to use

After requirements are gathered and before any data is touched. Planning is especially important when the analysis involves multiple steps, uncertain data availability, or a tight deadline where sequencing matters. A 15-minute planning session prevents hours of wrong-direction work.

Process

  1. Decompose the question — break the business question into sub-questions using references/scoping_framework.md; each sub-question should be answerable with a single data pull or calculation.
  2. Identify data dependencies — for each sub-question, list the required tables/datasets and assess availability (confirmed / likely / unknown); flag blockers early.
  3. Sequence the work — order sub-questions so that each output feeds the next; identify which steps can run in parallel.
  4. Estimate effort — use references/effort_estimation.md to assign time estimates per step; sum to a total and compare against the deadline.
  5. Log risks and dependencies — use references/risks_dependencies.md to document anything that could delay or invalidate the plan (data gaps, external approvals, methodology uncertainty).
  6. Produce the plan — fill in assets/analysis_plan_template.md; for projects with stakeholder kickoffs use assets/kickoff_doc_template.md.

Inputs the skill needs

  • Analysis brief or requirements doc (from stakeholder-requirements-gathering skill)
  • Available data sources
  • Deadline and resource constraints

Output

  • Completed analysis plan with sequenced steps and time estimates (analysis_plan_template.md)
  • Kickoff doc for stakeholder alignment (optional, kickoff_doc_template.md)
  • Risk / dependency log

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides a structured framework and templates for data analysis planning. It contains no executable code, network requests, or sensitive data access, and is safe to use.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 9449d36. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 7 months ago

README badge

README badge for nimrodfisher/data-analytics-skills/analysis-planning