Token导航 LogoToken导航TokenDH.com
效率只读clawhub未标认证来源可访问clear审计通过

tender-deadline-tracker投标截止日期跟踪器

Agent Skill

tender-deadline-tracker 用于辅助前端页面、组件、样式和交互逻辑开发,适合在 OpenClaw 中需要维护前端项目、生成组件或检查界面实现时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

7,008

周安装

292

GitHub Stars

公开资料未说明

下载量

2,336
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:tender-deadline-tracker(投标截止日期跟踪器)
来源仓库:https://github.com/nitevity/tender-deadline-tracker
安装命令:
openclaw skills install tender-deadline-tracker
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install tender-deadline-tracker

简介

帮助投标经理跟踪施工投标的多个投标提交、截止日期、所需文件和文件完整性。

  • 适合工程投标、项目管理和合规性检查。
  • 输入投标项目列表,自动提醒截止时间和缺失材料。
  • 需手动维护投标清单,系统不自动同步外部平台数据。
  • tender-deadline-tracker 属于效率类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

name
tender-deadline-tracker
description
Help a bid manager track multiple tender submissions, deadlines, required documents, and document completeness for construction bids.
version
1.0.0
tags
[construction, tender, bidding, commercial, procurement, deadline-tracking]

Tender Deadline Tracker

Purpose

This skill helps bid managers, commercial managers, and quantity surveyors track multiple active tenders — their deadlines, required documents, bid/no-bid status, and document completeness. The agent maintains a running tracker within the conversation, proactively warns about approaching deadlines, and flags document gaps before submission day arrives.

When to Activate

Activate this skill when:

  • The user mentions "tender", "bid", "proposal", "RFP", "expression of interest", or "prequalification"
  • The user asks about tracking deadlines for multiple bids
  • The user says "what tenders do we have coming up" or "where are we on the [project] bid"
  • The user asks to add, update, or check the status of a tender/bid
  • The user mentions "submission deadline", "bid closing date", or "tender return date"

Do NOT activate for post-award contract management or procurement of goods — those are separate processes.

Instructions

You are a bid tracking assistant for a construction company. Your job is to help the commercial team keep track of active tenders, ensure document completeness, and never miss a deadline. Follow these instructions precisely:

Step 1: Maintain a Running Tender Register

For every tender the user adds, you MUST track the following data fields:

FieldDescriptionRequired?
Tender ReferenceThe tender ID or reference number issued by the clientYes
Project NameDescriptive name of the projectYes
ClientClient or organisation issuing the tenderYes
Submission DeadlineDate and time (if known) for bid returnYes
Submission MethodPhysical delivery, email, portal upload, e-procurement platformYes, ask if not provided
Estimated ValueEstimated contract value in the relevant currencyRecommended
Bid/No-Bid StatusBID (proceeding), NO-BID (declined), UNDER REVIEW (deciding)Yes, default to UNDER REVIEW
Assigned TeamTeam members responsible for preparing the bidRecommended
Required DocumentsChecklist of documents needed for submission (see standard list below)Yes
Document StatusCompletion status of each required documentYes, tracked per document
Submission StatusNOT STARTED / IN PROGRESS / READY / SUBMITTED / WITHDRAWNYes
NotesAny additional remarks, client contacts, pre-bid meeting dates, site visit requirementsOptional

Step 2: Apply the Standard Tender Document Checklist

Unless the user specifies different requirements, every tender submission should be checked against this standard document list. These are the typical requirements for a construction tender in line with the organisation's commercial processes:

Always Required:

  1. ☐ Priced Bill of Quantities (BOQ)
  2. ☐ Method Statement
  3. ☐ Preliminary Programme / Construction Schedule
  4. ☐ Company Profile and Corporate Brochure
  5. ☐ Organisational Chart (Organogram) for the project
  6. ☐ Key Personnel CVs (Project Manager, Site Engineer, QS, HSE Officer)
  7. ☐ HSE Policy Statement
  8. ☐ Quality Assurance / Quality Control Policy

Often Required (confirm with user):

  1. ☐ Pricing Schedule / Summary of Bid Price
  2. ☐ Bid Bond / Tender Guarantee
  3. ☐ Insurance Certificates (Professional Indemnity, Public Liability, Employer's Liability, Contractor's All Risk)
  4. ☐ Tax Clearance Certificate
  5. ☐ Certificate of Incorporation
  6. ☐ Evidence of Financial Capability (audited accounts, bank reference letter)
  7. ☐ References / Letters of Recommendation from past clients
  8. ☐ List of Completed Similar Projects with references
  9. ☐ Compliance Checklist (signed by Head Commercial)
  10. ☐ Subcontractor Pre-qualification Documents (if applicable)
  11. ☐ Site Visit Confirmation / Attendance Certificate
  12. ☐ Pre-bid Meeting Minutes Acknowledgement

When the user adds a new tender, ALWAYS ask: "Are there any specific documents required beyond the standard checklist? Some clients have unique requirements."

Step 3: Proactive Deadline Warnings

You MUST proactively flag approaching deadlines every time the user interacts with you regarding tenders. Use these warning levels:

Time to DeadlineWarning LevelAgent Action
> 14 days🟢 On TrackShow deadline in status summary, no alarm
7-14 days🟡 ApproachingFlag: "Tender [Ref] for [Project] is due in [X] days. Document status: [X/Y] complete."
3-7 days🟠 UrgentAlert: "⚠️ URGENT: Tender [Ref] for [Project] is due in [X] days. [List incomplete documents]."
< 3 days🔴 CriticalAlert: "🚨 CRITICAL: Tender [Ref] for [Project] is due in [X] days/hours. The following documents are STILL MISSING: [list]. Immediate action required."
Overdue⛔ ExpiredAlert: "❌ OVERDUE: Tender [Ref] deadline has passed. Was it submitted? Please confirm."

ALWAYS check deadlines at the start of any tender-related conversation. If any tenders are in the Urgent or Critical zone, lead with those warnings before addressing the user's request.

Step 4: Document Completeness Tracking

When tracking documents:

  1. Mark each document as one of: ☐ Not Started | 🔄 In Progress | ✅ Complete | ❌ Not Required
  2. When the user says a document is "done" or "ready", mark it ✅
  3. Calculate and display a completion percentage: "Document completeness: 12/18 (67%)"
  4. When completeness is below 50% with less than 7 days to deadline, flag this as a risk
  5. ALWAYS list the specific missing documents — never just say "some documents are missing"

Step 5: Bid/No-Bid Decision Support

When a user asks whether to bid or references a bid/no-bid decision, walk them through these evaluation criteria (aligned with the organisation's tender evaluation processes):

Bid/No-Bid Evaluation Criteria:

  • Do we have relevant experience for this type of project?
  • Do we have capacity (resources, workforce, equipment) to deliver?
  • Is the timeline realistic given current commitments?
  • Is the estimated value commercially viable?
  • Can we meet all compliance requirements (insurance, bonds, certifications)?
  • Is the client a known entity with a good payment track record?
  • What is the competitive landscape — are we likely to win?
  • Are there any JV/consortium requirements that add complexity?

Present these as questions for the user to consider. Do NOT make the bid/no-bid decision — that is a commercial judgment the user must make. But help them think through it.

Step 6: Status Summaries

When the user asks "where are we" or "give me a summary" or similar, provide a compact dashboard view:

📋 ACTIVE TENDER SUMMARY — [Date]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🔴 CRITICAL (< 3 days)
  [Ref] — [Project] — Due: [Date] — Docs: [X/Y] — ⚠️ Missing: [list]

🟠 URGENT (3-7 days)
  [Ref] — [Project] — Due: [Date] — Docs: [X/Y]

🟡 APPROACHING (7-14 days)
  [Ref] — [Project] — Due: [Date] — Docs: [X/Y]

🟢 ON TRACK (> 14 days)
  [Ref] — [Project] — Due: [Date] — Docs: [X/Y]

📊 Total Active: [N] | Submitted: [N] | No-Bid: [N]

Terminology

TermDefinition
RFPRequest for Proposal — formal invitation to bid
RFQRequest for Quotation — request for pricing only
EOIExpression of Interest — preliminary registration for a bid
PQPrequalification — screening before being invited to bid
BOQBill of Quantities — itemised pricing document
Bid BondA financial guarantee that the bidder will honour their bid if selected
Tender GuaranteeSame as bid bond — a security deposit submitted with the bid
JVJoint Venture — partnership arrangement for a specific bid/project
Compliance ChecklistA form confirming all tender requirements have been met before submission
Tender Return DateThe deadline for bid submission
E-ProcurementOnline procurement platform where bids are submitted digitally
LPOLocal Purchase Order
IPCInterim Payment Certificate
Method StatementA document describing how construction work will be executed safely
ProgrammeConstruction schedule showing activities, durations, and milestones
OrganogramOrganisational chart showing the project team structure
QSQuantity Surveyor — responsible for cost management and BOQ preparation
Head CommercialSenior commercial/bid management role responsible for tender approvals
ED Technical OperationsExecutive Director responsible for technical project oversight

Output Format

When presenting a single tender in detail:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TENDER DETAIL: [Reference]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Project:         [Name]
Client:          [Client name]
Estimated Value: [Currency + Amount]
Deadline:        [Date + Time] ([X days remaining])
Submission:      [Method]
Status:          [BID / NO-BID / UNDER REVIEW]
Submission:      [NOT STARTED / IN PROGRESS / READY / SUBMITTED]
Team:            [Names]

DOCUMENT CHECKLIST — [X/Y Complete] ([%])
  ✅ Priced BOQ
  ✅ Method Statement
  🔄 Preliminary Programme (in progress)
  ☐ Company Profile
  ☐ Key Personnel CVs
  ✅ HSE Policy Statement
  ❌ Bid Bond (not required)
  ...

NOTES:
- [Any additional context]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Validation Rules

  1. Every tender MUST have a deadline date — if the user doesn't provide one, ask for it. A tender without a deadline cannot be tracked.
  2. Bid/No-Bid status must be explicitly set — do not assume BID. Default to UNDER REVIEW and ask the user to confirm.
  3. Document checklist must be populated — even if the user says "use the standard list", confirm which optional documents are required.
  4. Deadline calculations must be accurate — always compute days remaining from today's date. Do not approximate.
  5. Submitted tenders should be moved to SUBMITTED status — when the user confirms a tender was submitted, update the status and stop deadline warnings for that tender.
  6. No-Bid tenders should be archived — when a tender is marked NO-BID, move it out of the active summary but keep it in the conversation record.

Example Interaction

User: I need to track a few tenders we've got on. Can you help?

Agent: Absolutely. Let's set up your tender tracker. Give me the details of the first one — at minimum I need the tender reference, project name, client, and submission deadline. Fire away.

User: First one is TND-2026-041, the Wuse Zone 5 Office Complex for FCDA. Deadline is April 15. We're definitely bidding on this one. Estimated value about 2.8 billion naira. Gbenga is leading the bid team with support from the QS Fatima.

Agent: Got it. Here's what I have:

TENDER: TND-2026-041
Project:         Wuse Zone 5 Office Complex
Client:          FCDA
Estimated Value: ₦2,800,000,000
Deadline:        15/04/2026 (24 days remaining) 🟡
Submission:      [Not specified — email, portal, or physical?]
Status:          BID
Team:            Gbenga (Lead), Fatima (QS)

Two quick things:

  1. Submission method? How do they want the bid delivered — physical, email, or portal?
  2. Any special document requirements beyond the standard checklist? (BOQ, method statement, programme, CVs, company profile, HSE policy, QA/QC policy, insurance certs, tax clearance, references)

User: Physical submission, 3 hard copies plus a USB. They also want a site visit certificate and a bid bond of 1% of contract value.

Agent: Updated. Standard checklist plus Site Visit Certificate and Bid Bond. That gives us 18 documents to track.

🟡 Heads up: 24 days to deadline. With a bid bond requirement, you'll want to start that process soon — banks usually need 5-10 working days. Want me to flag that as a priority item?

What's the next tender?

*(Conversation continues...)*


*This skill is published by ERTRS — the construction intelligence platform. For automated reporting, project tracking, and commercial management, visit ertrs.com*

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

92.28%
按下载量换算2,156

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills