Results for “report”

Drafts an Adverse Event Reporting Policy compliant with 21 CFR 312.32 (IND safety reporting), 21 CFR 314.80 (postmarketing), and ICH E2A, with multi-jurisdictional overlays (EMA, PMDA, Health Canada). Covers seriousness/causality frameworks, expedited reporting timelines, roles, documentation standards, training mandates, and QA mechanisms. Use when drafting or updating an adverse event reporting policy, pharmacovigilance policy, AE/SAE reporting SOP, or safety reporting framework for a pharmaceutical company, CRO, biotech, or clinical research institution.

The English summary is being prepared. Showing the original description.

Shared setup and rules for the report-skills bundle (report-publisher, client-reporter, proposal-tracker, deck-publisher, report-designer). Loaded by the individual skills for the common ReportRoom MCP publish flow, account bootstrap, and safety gates. Not invoked directly — pick the specific skill for the job.

The English summary is being prepared. Showing the original description.

SF CLI経由でSalesforceレポートを作成するスキル。Metadata APIとREST APIの使い分け、フィールド命名規則、列数制限、レポートタイプ設定を網羅。カスタムオブジェクトレポート作成時の注意点も含む。Use when creating Salesforce reports via CLI, deploying report types, or automating report generation.

The English summary is being prepared. Showing the original description.

ESG(環境・社会・ガバナンス)レポート作成支援スキル。GRI、SASB、TCFD、CDP等の国際基準に準拠した サステナビリティレポート作成、マテリアリティ分析、KPI設定、データ収集・開示をサポート。 Use when creating sustainability reports, conducting materiality assessments, setting ESG targets, or preparing disclosures aligned with GRI, SASB, TCFD, CDP, or CSRD standards. Triggers: "ESG report", "sustainability report", "TCFD", "GRI", "SASB", "CDP", "materiality assessment", "carbon footprint".

The English summary is being prepared. Showing the original description.

Turns sustainability or ESG reports the user provides into a DRAFT question pack for reviewers: every quantitative disclosure as stated with unit, period, boundary and page, year-over-year changes computed only from the stated figures with the arithmetic shown, targets with stated and computed progress, restatements and inconsistencies, gaps and specific questions to the report owner. No assurance, accuracy or conformance verdict. Use when the user asks to "prepare review questions on our sustainability report", "what changed year on year in this ESG report", "check the figures in this report before it goes to the board", "find the gaps in this ESG disclosure" or "build a question pack for the report owner". Do not use for reviewing marketing text against environmental-claim rules, use green-claims-review instead. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

Prepares the trend update for a recurring emailed report: identifies report emails not yet processed, extracts the configured metrics from their spreadsheet, CSV or PDF attachments, returns new rows for an append-only trends sheet and writes a DRAFT summary with period-on-period deltas and flagged anomalies. Use when the user asks to "update the trends for the weekly report", "analyse the latest monthly report", "what changed in the latest report", "do the latest numbers look unusual" or "set up tracking for a report that arrives by email". Do not use for a single file with no trend state, use dataset-insight-pack instead. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

Assess OpenClaw security reports against released versions and documented trust boundaries, which define trusted users and components. Gather evidence to recommend closing, keeping open, or narrowing a report, and draft a maintainer response.

• Assessing an OpenClaw security report
• Checking whether released versions contain a reported bug
• Comparing a report with existing advisories

Turn local Claude Code session history into a personal activity report, cross-checked with local Git history. Generate Markdown and standalone HTML showing project activity, touched files, related commits, and each project's share of compute usage.

• Explaining Claude Code usage to a manager
• Reviewing monthly activity across projects
• Preparing evidence for a personal performance review

Turn local Q&A session files into an English weekly report with topic rankings, unresolved issues, activity metrics, and comparisons with the previous week. Include supporting message excerpts and structured data for later document and dashboard rendering.

• Create a weekly community Q&A report
• Compare topics and activity with the previous week
• Review unresolved high-priority issues

Turn defects found during Oracle-to-PostgreSQL migration into structured bug reports. Document expected and actual behavior, reproduction steps, severity, root causes, proposed changes, and validation on both databases so teams can act on the findings.

• Documenting behavioral differences found during migration
• Organizing reproduction steps and test data
• Recording fixes, affected files, and validation steps

Turn cyber threat intelligence reports into a searchable library of attacker behaviors linked to MITRE ATT&CK techniques. Export structured STIX 2.1 data, a threat information exchange format, and create detection rule templates from documented activity.

• Cataloging attacker behaviors from threat intelligence reports
• Organizing attack patterns by tactic, technique, and threat actor
• Creating detection rule templates from documented behaviors

Turn project or team updates into a structured report for leaders and stakeholders. The skill summarizes key metrics, accomplishments, ongoing work, risks, decisions needed, and next-period priorities, with an overall assessment of whether work is on track.

• Write weekly, monthly, or quarterly progress reports
• Summarize progress against key metrics and targets
• Highlight risks and decisions needing stakeholder attention

Assess FastMCP vulnerability reports by preserving evidence, reproducing claims, and identifying which component owns the failed protection. Establish affected versions and realistic impact, review proposed fixes, and recommend how the report should be handled.

• Assessing vulnerability reports and bug bounty submissions
• Separating OAuth proxy issues from deployment problems
• Checking affected versions and realistic impact

Create a game playtest report template or turn session notes into organized feedback. Separate gameplay problems from bugs, compare observations with design intent, and identify priorities for design changes, balance adjustments, and polish.

• Preparing a playtest report template
• Organizing raw playtest notes
• Separating gameplay issues from bugs

Recheck older NemoClaw bug reports against the reported and newest releases, then prepare evidence-backed recommendations for maintainers. It documents reproduction results and proposed updates for approval without automatically closing issues.

• Rechecking older bug reports
• Comparing reported and newest releases
• Preparing evidence-backed issue updates

Create charts, dashboards, scorecards, and styled summaries as standalone HTML reports for the screenpipe viewer. Keep styles, scripts, and images inside the file so the report renders in a sandbox with no network access.

• Create a visual report of daily work time
• Present key metrics in a dashboard
• Summarize results with charts and scorecards

Assess Web3 vulnerability findings before submission by checking scope, reproducibility, prerequisites, and attack costs. Organize the root cause, measurable impact, working proof of concept, and proposed fix into an Immunefi report, with examples for comparison.

• Checking whether a finding is ready for submission
• Drafting an Immunefi vulnerability report
• Reviewing reproduction code and measurable impact

Turn existing GEO audits, which assess readiness for AI search citations, into one client report. Combine scores, technical and content findings, platform comparisons, and a prioritized action plan written for business owners and marketing leaders.

• Combining multiple GEO audits into a client report
• Explaining AI search readiness to business leaders
• Prioritizing improvements by impact and effort

Extract text from existing PDFs and assemble it into a new PDF report using command-line tools. Choose an available conversion method, combine source content, and check the resulting file’s pages and included text.

• Combine content from several PDFs into one report
• Extract text from selected PDF pages
• Generate PDF reports without Python PDF libraries

Create PDF reports from existing PDFs using command-line tools. The workflow checks source files, extracts text, organizes report sections, and generates or merges PDFs, with alternative output methods depending on the tools available.

• Building a report from several source PDFs
• Checking PDF page counts and required terms
• Extracting text from selected PDF pages

Create PDF checklists, reports, and scorecards with Python in a sandbox, an isolated code execution environment. The workflow covers choosing a library, arranging headings and tables, generating the document, and checking that the output file exists.

• Creating a PDF checklist for distribution
• Organizing assessment results into a scorecard
• Producing reports with headings and tables

Download PDFs or process local files, extract their text, and turn processed data into structured PDF reports with ReportLab. Includes alternative extraction methods and text output when PDF generation fails.

• Extracting text from technical manuals
• Processing PDFs downloaded from websites
• Creating PDF reports with sections and tables

Troubleshoot PDF creation by trying pandoc, then reportlab, then fpdf2. Check tool availability, install missing Python libraries as needed, run generation with an explicit working directory, and verify that the output file exists.

• Converting Markdown or HTML to PDF
• Trying another tool after PDF generation fails
• Checking PDF tools and installing missing libraries

Handle one known local bug or testable bug hypothesis through reproduction, independent validation, repair, and regression checks. Produce a local patch commit and evidence reports that help reviewers judge whether the fix is ready.

• Investigate and repair one reported local bug
• Have separate agents verify reproduction and the fix
• Prepare evidence reports for patch review