Cybersecurity Product Bid Metric Evaluator

Problem

Before responding to cybersecurity product tenders, the hard part is often not writing the response document, but mapping tender technical requirements back to product evidence. Bidders need to know which clauses are mandatory, which carry ★ or ▲, and whether they cover functionality, performance, certifications, deployment, or service commitments. Performance numbers must be checked strictly, qualification materials must be traceable, and compound requirements may hide multiple sub-points. Guessing from general product familiarity can miss negative deviations, misjudge borderline metrics, or create internal review failures.

Workflow

The skill turns this into a reviewable process. It first clarifies the tender source, reference document directory, and output location. It then inventories whitepapers, product manuals, test reports, certifications, and solution documents, building a material map and evidence index. Tender clauses are parsed into a structured list that preserves original wording, requirement level, importance markers, and verifiable key points. For each item, the skill retrieves evidence, quotes original text, applies a four-level rating, and suggests an answer strategy. Numeric metrics are compared by value, compound metrics are judged by the weakest sub-point, and missing evidence is recorded as not satisfied rather than inferred. The final Markdown report includes an executive summary, satisfaction statistics, major risk list, and line-by-line evaluation table for internal bid/no-bid decisions.

Boundaries

Use it for tender specification compliance checks, pre-response clause review, reusing one product evidence base across bids, and internal review of evidence coverage. It does not replace full technical proposal writing and is not necessarily the best fit for compliance certification assessment alone. If the task is simply “does the product have feature X,” reading the documentation directly is lighter.