Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- Raw▲ **Answer:** Extend Fieldbook to the North and Islands in Q1 — but only after redesigning onboarding to match the rapid adoption seen in Central and East and addressing the two integration gaps (asset‑register feed and invoicing code mapping). **Situation** – You have seen the two‑quarter rollout in four regions: adoption reached 83 % of work orders, scheduling density rose 15 % and travel time fell 18 %, delivering clear operational and financial gains. **Complication** – Adoption lagged in...Votes: 0GitHub stars: 2
- RawFieldbook has improved operating efficiency in the four live regions and paid back within the second quarter in Central and East. However, South and West show that an underprepared rollout remains at break-even and can leave a new region underwater for at least two quarters. The COO should approve a conditional Q1 extension, releasing each region only after onboarding, integration ownership, and a repeatable go-live review are in place.Votes: 0GitHub stars: 2
- Raw**To unblock the compliance track today: send the architecture diagram now, escalate the stalled dependency-list request straight to Okafor, and get written answers on pentest scope and Lisbon working before they stall further.** **Already settled — no action needed:** - A security review is mandatory before production; whether a penetration test is also required is decided *during* that review. - Aldergate's internal hardening framework exists but doesn't substitute for the review. - Working...Votes: 0GitHub stars: 2
- Raw**Compliance digest — bottom line:** security requirements remain unconfirmed (open since 3 May), so build-phase pricing cannot be fixed. Aldergate has confirmed the review mechanics, but three substantive items still need its input — the approved-package list, the architecture-dependent data-storage answer, and Lisbon staffing confirmation — plus a process gap: no direct access yet to the information-security owner. - **Security review:** mandatory before production; whether a penetration te...Votes: 0GitHub stars: 2
- Raw**Action Required Today:** Send the draft architecture diagram to Aldergate immediately to unlock the data storage and encryption answers, and escalate the approved-package list delay to force a delivery date; these are the only blockers preventing us from fixing the build-phase price. **Outstanding Gaps** • **Data storage & encryption:** Aldergate declined to answer without an architecture diagram (Gate Review Q7). A draft exists since 11 August but was not shared at the 9 July sync. Sending...Votes: 0GitHub stars: 2
- Raw**Subject: Unblock pricing today: Send architecture diagram and escalate package list** Build-phase pricing is stuck because security requirements are unconfirmed. Aldergate declined to answer data storage questions without our architecture diagram, and the approved-package list is 98 days overdue with no delivery date. To unblock pricing today, send the draft architecture diagram and escalate the package list delay. ● **Send draft architecture diagram to Aldergate** ○ Triggers answer to Q7 (...Votes: 0GitHub stars: 2
- Raw**The compliance track is blocked on us, not on Aldergate: send the architecture diagram today and get a dated commitment from Okafor directly — three of the four open items can't move until those two things happen.** **What is already answered (treat as settled, don't re-ask)** - A security review before production is mandatory, and a penetration test may be added inside it — so the build price cannot be fixed to a scope until the review is underway (Q1, Q2; R-07 open since 3 May). - Buildin...Votes: 0GitHub stars: 2
- Raw**Three moves unblock pricing:** 1. **Send the architecture diagram to Aldergate today.** (Ready 11 Aug. Unblocks Q7: storage, encryption, logging.) 2. **In the same message, ask: is Lisbon acceptable?** (Gate review approves Ireland only; you have two engineers in Lisbon. Needs yes/no.) 3. **Escalate the approved-package list.** (Promised 12 May, re-promised 9 July—98 days overdue. Copy S. Okafor [information security owner] directly; Whitcombe is filtering.) **Already confirmed:** Security ...Votes: 0GitHub stars: 2
- Raw**Answer:** The compliance track is partially answered – we know the security review is required, an internal hardening framework exists, an open‑source policy is in place, dependency approval will be assessed during the review, and Fernway staff can work from Ireland – but we still need the approved‑package list, the architecture diagram (to resolve data‑storage, encryption and logging questions), and a defined turnaround time for dependency approvals. **What is already answered** - **Securi...Votes: 0GitHub stars: 2
- RawCompliance is not yet sufficient to price the build: send Aldergate the draft architecture today and secure named-owner responses on packages, architecture requirements, and Lisbon access. Already answered: a security review is mandatory before production; any penetration test and critical-dependency assessment are decided within that review; an internal hardening framework and open-source policy exist; Ireland-based work is acceptable. Still needed from Aldergate: the approved-package list (...Votes: 0GitHub stars: 2
- RawSubject: We should use next sprint to cut the defect backlog Alex — the defect backlog is now hurting revenue, not just engineering hygiene, and I recommend we spend next sprint reducing it. Backlog is growing faster than we close it, and on current trend it roughly doubles within a year (see chart). That backlog is costing us in three ways: 1. **Customers are leaving.** Churn tracks defect volume directly (see chart), and CX/Research interviews show customers citing bugs as the reason they l...Votes: 0GitHub stars: 2
- RawSubject: Next sprint: reduce the defect backlog before it drives churn and lost deals Alex, The attached chart compares incoming and fixed defects and projects the backlog one year ahead. Customer Experience and Research report that defects are contributing to churn. I recommend we use the next sprint to reduce the defect backlog. Why: 1. We will face a persistent backlog: the one-year projection shows the trajectory of incoming versus fixed defects. 2. We are losing customers: a second chart...Votes: 0GitHub stars: 2
- RawSubject: Dedicate next sprint to reducing defect backlog We are finalizing the plan for the next sprint. Our defect backlog is growing faster than we can resolve it, creating immediate risks to revenue, brand reputation, and long-term stability. To address these compounding issues, should we dedicate the next sprint to reducing the defect backlog? Yes. Prioritizing backlog reduction now delivers three critical outcomes: 1. **Stop immediate revenue loss and churn.** Defect volume directly driv...Votes: 0GitHub stars: 2
- RawSubject: Proposal: Dedicate next sprint to reducing defect backlog As we plan the next sprint, the defect backlog is growing faster than we can fix it, projecting a significant increase over the coming year. This accumulation is now driving customer churn, triggering complaints from major accounts, and hindering Sales close rates. We should dedicate the next sprint to reducing the defect backlog. This prioritization addresses three critical areas: 1. **Protect Revenue:** Defects are directly ...Votes: 0GitHub stars: 2
- RawHi Alex, **Let's dedicate the next sprint to cutting the defect backlog.** We are closing fewer defects than we take in, and the cost of that gap has moved from engineering into revenue. **1. The backlog will not correct itself.** New defects have outpaced fixes for long enough that the trend is stable, and the one-year projection from that trend shows the gap widening rather than levelling off (chart 1). **2. Defects are already costing us existing customers.** Customer Experience and Resear...Votes: 0GitHub stars: 2
- Raw**Subject:** Focus next sprint on reducing the defect backlog Our data shows defects are driving customer churn and blocking deal closure. We should make defect reduction our next sprint priority. Why this matters: - We're losing customers directly to defects (CX data and customer interviews confirm) - We're losing deals due to defect concerns (Sales reports) - The backlog is growing unsustainably (our one-year projection shows incoming will outpace fixes) Let me know if you'd like to review ...Votes: 0GitHub stars: 2
- RawSubject: Prioritize reducing the defect backlog in the next sprint Situation: Our product is currently facing a growing defect backlog; the attached chart shows new defects outpacing closures and projects a larger backlog in a year. Complication: Defects are now a key driver of churn (customer‑experience data and churn‑vs‑defect chart) and are harming our brand and sales—evidenced by negative user posts, a complaint from a major account, and falling close rates reported by Sales. Answer: We s...Votes: 0GitHub stars: 2
- RawSubject: Make defect-backlog reduction the next sprint’s focus The defect backlog is growing faster than we are closing it and is projected to worsen over the next year. We should use the next sprint to reduce it because it is now affecting: 1. Retention — Customer Experience data, churn trends alongside defect volume, and user interviews link defects to customer loss. 2. Revenue — a major-account complaint, user posts, and Sales reports show defects are damaging trust and making deals harder...Votes: 0GitHub stars: 2
- Raw**Legend:** ▲ top/answer · ● first-level group · ⚠ violation · ↑ buried conclusion · ⇄ wrong order · ⊕ gap ```text ▲/⚠ This memorandum describes how project teams identify and deliver significant profit improvements. [statement of purpose — names the topic, answers nothing] It is organized in six sections: ● Background [⚠ not same-kind with rest] ● Principles of the project-team approach [⚠ mixed kind] ● Definition of project work ...Votes: 0GitHub stars: 2
- Raw**Legend** ▲ top / answer · ● first-level group · ○ supporting detail · ⚠ violation · ↑ conclusion buried lower than it belongs · ⇄ wrong order type here · ⊗ overlap (ME broken) · ⊕ gap (CE broken) · ✂ cut, or move to an appendix **Annotated opening** ```text ⊕ This memorandum describes how project teams identify and deliver significant profit improvements. [⚠ Topic label / statement of purpose; no answer or SCQ question visible.] It is organized in six sections: [✂ Contents statement; not an...Votes: 0GitHub stars: 2