Skip to content

Repository files navigation

Agent Customizations In This Repository

Temporal Slicing Adjustment Banner

This folder contains workspace-scoped agent customizations for BCNexus.

Temporal Slicing Workflow Map

Temporal Slicing Reuse

If you want to reuse the temporal slicing planning workflow in another repository, you do not need to clone all of BCNexus into that repository.

Minimum files to copy

Copy these into the target repository with the same relative paths:

  • .github/skills/temporal-slicing-adjustment/SKILL.md
  • .github/skills/temporal-slicing-adjustment/references/workflow-surfaces.md

Optional prompt trigger

Tip

Developer recommended.

If you also want a ready-made slash command, copy:

  • .github/prompts/timeslice-plan.prompt.md

This exposes the /timeslice-plan prompt in chat.

How Another Team Should Use It

Option 1: Skill only

Copy the temporal-slicing-adjustment skill folder into the target repository.

Then ask the agent naturally, for example:

Use the temporal-slicing-adjustment skill to plan how temporal aggregation should fit into this workflow.

Option 2: Skill plus prompt

Tip

Developer recommended.

Copy both the skill folder and .github/prompts/timeslice-plan.prompt.md.

Then run:

/timeslice-plan I need to add representative-day temporal aggregation to my OSeMOSYS workflow.

If the workflow structure is unclear, the prompt is designed to make the agent ask follow-up questions before planning.

What The Skill Assumes

The skill has two layers:

  • Repo-specific guidance using BCNexus as the worked example.
  • Framework-general guidance for other OSeMOSYS or CLEWs workflows.

When copied into another repository, the general guidance is immediately reusable. The BCNexus-specific file references remain a worked example unless BCNexus is also present in the workspace.

Storage Limitation

The current storage-specific guidance is directly grounded in the storage structures used here and in Delta E's storage work for temporally aggregated OSeMOSYS models.

Directly supported storage structures:

  • Niet
  • Kotzur

If another workflow uses different storage algorithms, the agent should ask about them explicitly and treat storage-specific mapping as uncertain until the relevant structure is provided.

Reference repositories:

Recommended Setup For Comparison Work

If you want the agent to compare another model directly against BCNexus, use a multi-root workspace or clone BCNexus alongside the target repository.

That is usually better than nesting BCNexus inside the other repository as a subdirectory.

Author

This temporal slicing skill was authored for the BCNexus workflow by Md Eliasinul Islam.

For background on the author or to reach out about using or adapting this skill, see eliasinul.com.

About

Visit website for relevant updates

Topics

Resources

Stars

4 stars

Watchers

2 watching

Forks

Releases

Sponsor this project

Packages

Contributors

Languages