grant application packager

Engineering Community

Skill notes

Core Workflow

Gather the source material, existing conventions, templates, and destination format before drafting. Extract the information that matters most for the intended audience and discard low-signal noise. Structure the output so it matches repo, team, or domain expectations instead of starting from a blank generic outline. Draft the artifact, then surface any missing facts or decisions that still need human input.

Deliver

A ready-to-edit draft in the expected structure and tone. The main sections, decisions, or states the artifact should include. Open questions or missing facts that would improve the final output.

Guardrails

Do not invent facts, metrics, approvals, or guarantees that are not supported by the inputs. Prefer existing repo or team conventions over generic formatting. Keep the output useful and specific rather than padded. Do not fabricate citations, sources, or evidence; keep claims tied to the provided material.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@00PrabalK00 · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Grant Application Packager

## Overview

Organize grant proposal sections, milestones, evaluation plans, and impact framing into a coherent application package.

## Core Workflow

1. Gather the source material, existing conventions, templates, and destination format before drafting.
2. Extract the information that matters most for the intended audience and discard low-signal noise.
3. Structure the output so it matches repo, team, or domain expectations instead of starting from a blank generic outline.
4. Draft the artifact, then surface any missing facts or decisions that still need human input.

## Deliver

- A ready-to-edit draft in the expected structure and tone.
- The main sections, decisions, or states the artifact should include.
- Open questions or missing facts that would improve the final output.

## Guardrails

- Do not invent facts, metrics, approvals, or guarantees that are not supported by the inputs.
- Prefer existing repo or team conventions over generic formatting.
- Keep the output useful and specific rather than padded.
- Do not fabricate citations, sources, or evidence; keep claims tied to the provided material.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.