Stackyapper Ideas

Using Stackyapper, plan the dispatch board for [team] on [date]. [Technician] is out. Confirm the service board, company scope, and connected accounts before reading tickets and schedules. Use Code Mode when available for repeated reads. Prioritize customer impact and response deadlines, keeping booked visits and travel time. Return a proposed board with ticket, technician, time, reason, and source references. State pages and records read, unavailable sources, and how to continue any unfinished reads. Label incomplete coverage. Flag scheduling gaps; do not change assignments.

Using Stackyapper, investigate the recurring [issue] at [company], starting with [ticket or device]. Find related tickets, device events, and procedures in our connected apps. Compare the last three failures and separate evidence from possible causes. Give me an engineer handoff with source references, missing information, and next checks. Do not make changes.

Using Stackyapper, turn the steps from this [fictional or sanitized investigation] into a personal skill for [app]. Use only the investigation I provide. Read the skill-authoring guidance and check for an existing skill first. Keep the scope checks, tool discovery, paging limits, stop conditions, and handoff format. Remove record contents, names, and credentials. Show me the proposed skill for review before saving. If personal skills are disabled, return the text for review instead. Do not publish workspace guidance or run the investigation.

Using Stackyapper, draft a personal writing-style skill from these [fictional or approved sanitized samples] for [audience]. Use only the samples I provide; do not read my email or other connected records. Read the skill-authoring guidance and check for an existing style skill first. Describe tone, structure, wording preferences, and how to handle missing facts. Mark tentative preferences when the samples disagree. Include an invented example, without copying names or record contents. Show me the draft before saving. If personal skills are disabled, return the text for review instead. Do not publish workspace guidance or send a message.

Using Stackyapper, find why [team]’s service queue grew during [date range]. Confirm the service board and connected accounts. Use Code Mode when available for repeated reads of service and scheduling data. Compare ticket arrivals, reopenings, resolutions, and other movements, accounting for non-ticket work. Identify repeat issues and blockers. Give me a weekly service review with three proposed actions, owners, and source references. State pages and records read, unavailable sources, and how to continue unfinished reads. Reconcile totals only when coverage supports them; otherwise label observations from the records read. Do not rank technicians by closure counts.

Using Stackyapper, prepare a decision queue for [person or role] from [selected apps] during [period]. Confirm the workspace, connected accounts, priority rules, and page and record cap before reading. Use Code Mode when available for repeated reads. Group the records read into needs a decision, waiting on others, and reference. For each proposed decision, include why it needs attention, the recorded owner and due date if available, a source reference, and missing information. Separate recorded facts from inferred priority. Report unavailable sources, pages and records read, and unfinished reads. Do not send, archive, delete, assign work, or change records.

Using Stackyapper, compare this [dated prior brief] with current read-only records for [scope] in [selected apps]. Confirm the workspace, accounts, filters, and comparison dates. Match records using stable IDs or source references; flag unmatched items. Use Code Mode when available for repeated reads within an agreed page and record cap. Separate confirmed changes from items you could not recheck. Do not treat a missing record as resolved or deleted. Explain which changes need a decision, with source references and suggested next checks. Include both retrieval dates, pages and records read, unavailable sources, and coverage limits. Do not change records or send the brief.

Using Stackyapper, check whether [company] is ready for [migration] on [date]. Find the project plan, change record, restore-test evidence, and rollback procedure in our connected apps. Produce a go/no-go checklist with evidence, missing prerequisites, owners, and a proposed rollback cutoff. Do not execute or approve the migration.

Using Stackyapper, prepare a customer-facing business review for [company] covering [period]. Find relevant service history, agreements, asset risks, and previous commitments across our connected apps. Use our [organization doc skill] to create the document with a prioritized roadmap and questions for the customer. Separate service fixes from optional upgrades. Flag missing costs or plans; do not invent ROI or send it.

Using Stackyapper, assess whether [team] needs another hire for [period]. Find committed work, team availability, and pipeline in the relevant connected apps. Account for leave and support duties, keeping unsigned work separate. Produce a decision brief with the weekly capacity gap, temporary options, and a review date. Identify missing cost or ramp-time data.

Using Stackyapper, draft a quote for [company] for [request]. Use [pricing app] for approved prices and find the related discovery notes and agreement in our connected apps. Use our [organization doc skill] to format the draft. Include quantities, exclusions, and one-time versus recurring charges. Flag missing specifications or expired prices. Do not invent discounts, send the quote, or place an order.

Using Stackyapper, help us decide whether to bid on [RFP]. Find the relevant company credentials, references, and service details in our connected apps. Compare them with the RFP and addenda. Produce a requirements matrix with source sections, owners, evidence gaps, and submission deadlines, followed by a bid/no-bid brief. Flag unverified commitments rather than claiming compliance.

Using Stackyapper, prepare a license report for [company] from CIPP (Beta), if available to me. Confirm the customer tenant and define active as [activity definition]. Discover the current read tools and schemas, then retrieve users within an agreed page and record cap. Use Code Mode when available for repeated reads. Follow supported continuation and report incomplete coverage until completion is established. Use our [organization doc skill] to format names, licenses, activity status, and observed totals. Mark unavailable activity as unknown. Include the report date, retrieval scope, pages and records read, and any unfinished reads. Do not change licenses or send the document.

Using Stackyapper, assess profitability for [company] over [period]. Find agreements, actual revenue and credits, ticket time entries, and direct customer costs across our connected apps. Match work to its agreement and separate included support, projects, and out-of-scope work. Calculate labor cost using our loaded cost rates, not billing rates. Show contribution margin, the tickets consuming the most time, and unbilled work. Flag missing costs or time entries; do not treat them as zero. Use our [organization doc skill] to create an internal review with source references and questions for the account owner.