Hydropower Technical Proposal
Paste the following prompt into your AI chat to install this skill:
Please follow https://skillhub.cn/install/skillhub.md to install @user_eac1e28a/hydropowertechdoc.
About this skill
What problem it solves
Hydropower, network upgrade, monitoring, water-level, dam safety, and related project proposals are less about basic writing than about keeping group format, design depth, vendor comparison, and pricing evidence consistent. The source material expects body text in size-4 Chinese font, 24 pt line spacing, 22 mm margins, a signature block covering approval, review, verification, drafting, and date, and quantity lists in a standard three-line table format. Manual drafting often leads to missing sections, incomplete table headers, outdated standards, or untraceable price sources.
How it works
The skill follows the V5.0 flow for @user_eac1e28a/hydropowertechdoc: it parses project name, organization, type, budget, schedule, and scale, then selects base and optional sections. New projects usually use the 11-section standard structure. Renovation projects add “main existing problems” and multi-vendor comparison. Equipment replacement projects emphasize selection, parameter comparison, and disposal lists. Large engineering projects keep organization, quality assurance, and safety assurance sections.
Content generation targets technical and construction design depth. Each vendor proposal should include company background, architecture, functions, components, trade-offs, and case studies, followed by a comparison table. Pricing is sourced from bidding portals, vendor sites, JD/Tmall, and 1688, with the source recorded in the document. It then renders a Word file via scripts/generate_tech_doc.py and checks cover page, table of contents, numbering, fonts, spacing, table fields, and approval elements.
Boundaries
It fits hydropower and water-power projects such as new builds, upgrades, equipment replacement, monitoring systems, inspection systems, and anti-drone deployments. It is not intended for general writing, legal contracts, or non-technical documents. For group reporting or contract annexes, manual signatures, official seals, duplicate copies, and the latest valid standards must still be verified offline.
Use Cases
- Build a new hydropower monitoring system and draft a report-ready technical proposal in the 11-section group format.
- Upgrade dam safety monitoring with existing-problem analysis, multi-vendor comparison, and a three-line quantity table.
- Produce equipment replacement options with parameter comparison, disposal list, and sourced budget tables.
- Check large-project sections for organization, quality, safety systems, and signature block formatting.
Best For
- Hydropower engineering staff who need group-standard technical proposals for review.
- Project leads organizing documents for new builds, upgrades, and equipment replacement.
- Equipment selection engineers comparing multiple vendors with sourced pricing.
- Technical approvers checking section numbering, table fields, and signature blocks.
Related Skills
Reviews Chinese-law contract text via the accurLex API, returns the full review opinion, and exports a Word document.
Generates executable FAERS active-comparator safety comparison research plans focused on one SOC or PT family.
A reference framework for financial data analysis covering statements, KPIs, visualization, and reporting templates, without executing code or collecting data.
A knowledge-base-driven advisor for weak-current, network, and telecom equipment selection, covering parameter comparison, model recommendations, compatibility checks, and budgeting.