opencode-skills-collection 4.0.53 → 4.0.55

package/bundled-skills/internal-comms-anthropic/examples/faq-answers.md

@@ -1,3 +1,4 @@
+<!-- Modified in AAS on 2026-09-05. Audience, permissions and approved sources take precedence over template suggestions; draft only unless sending is authorized. -->
 ## Instructions
 You are an assistant for answering questions that are being asked across the company. Every week, there are lots of questions that get asked across the company, and your goal is to try to summarize what those questions are. We want our company to be well-informed and on the same page, so your job is to produce a set of frequently asked questions that our employees are asking and attempt to answer them. Your singular job is to do two things:
 

package/bundled-skills/internal-comms-anthropic/examples/general-comms.md

@@ -1,3 +1,4 @@
+<!-- Modified in AAS on 2026-09-05. Audience, permissions and approved sources take precedence over template suggestions; draft only unless sending is authorized. -->
   ## Instructions
   You are being asked to write internal company communication that doesn't fit into the standard formats (3P
   updates, newsletters, or FAQs).

package/bundled-skills/internal-comms-community/SKILL.md

@@ -1,11 +1,18 @@
 ---
 name: internal-comms-community
-description: "To write internal communications, use this skill for:"
+description: "Compatibility alias for internal-comms: draft status updates, newsletters and FAQs from approved sources."
 risk: safe
 source: community
 date_added: "2026-02-27"
 ---
 
+## Compatibility and maintenance
+
+Compatibility alias of `internal-comms`; use that ID for new references when no existing contract requires this one. The full instructions and support files remain local so existing installations
+continue to work offline. This is one shared procedure, not an additional capability.
+Preserve the callable ID when an existing manifest or client configuration uses it.
+Modified in AAS on 2026-09-05; original metadata and license notices are retained.
+
 ## When to use this skill
 To write internal communications, use this skill for:
 - 3P updates (Progress, Plans, Problems)
@@ -28,7 +35,19 @@ To write any internal communication:
     - `examples/general-comms.md` - For anything else that doesn't explicitly match one of the above
 3. **Follow the specific instructions** in that file for formatting, tone, and content gathering
 
-If the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.
+For other formats, use the provided audience/purpose and the general guide. Ask only for missing information that materially changes the draft.
+
+## Scope and example
+
+Use the supplied audience, date range and approved sources. Read only relevant
+accessible material; reactions, executive seniority and document views are not proof
+of accuracy. A private source does not automatically belong in a company-wide update.
+Drafting does not authorize sending, scheduling or publishing the communication.
+
+For a weekly 3P update, turn two confirmed shipped items, one next-week task and one
+open dependency into Progress/Plans/Problems. Preserve dates and uncertainty, link the
+source where appropriate and leave unknown metrics out. Expected handoff is a draft
+for the intended audience, not a claim that a message was sent.
 
 ## Keywords
 3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms

package/bundled-skills/internal-comms-community/examples/3p-updates.md

@@ -0,0 +1,48 @@
+<!-- Modified in AAS on 2026-09-05. Audience, permissions and approved sources take precedence over template suggestions; draft only unless sending is authorized. -->
+## Instructions
+You are being asked to write a 3P update. 3P updates stand for "Progress, Plans, Problems." The main audience is for executives, leadership, other teammates, etc. They're meant to be very succinct and to-the-point: think something you can read in 30-60sec or less. They're also for people with some, but not a lot of context on what the team does.
+
+3Ps can cover a team of any size, ranging all the way up to the entire company. The bigger the team, the less granular the tasks should be. For example, "mobile team" might have "shipped feature" or "fixed bugs," whereas the company might have really meaty 3Ps, like "hired 20 new people" or "closed 10 new deals."
+
+They represent the work of the team across a time period, almost always one week. They include three sections:
+1) Progress: what the team accomplished during the past reporting period. Focus mainly on things shipped, milestones achieved, tasks created, etc.
+2) Plans: what the team plans to do over the next time period. Focus on what things are top-of-mind, really high priority, etc. for the team.
+3) Problems: anything that is slowing the team down. This could be things like too few people, bugs or blockers that are preventing the team from moving forward, some deal that fell through, etc.
+
+Before writing them, make sure that you know the team name. If it's not specified, you can ask explicitly what the team name you're writing for is.
+
+
+## Tools Available
+Whenever possible, try to pull from available sources to get the information you need:
+- Slack: posts from team members with their updates - ideally look for posts in large channels with lots of reactions
+- Google Drive: docs written from critical team members with lots of views
+- Email: emails with lots of responses of lots of content that seems relevant
+- Calendar: non-recurring meetings that have a lot of importance, like product reviews, etc.
+
+
+Try to gather as much context as you can, focusing on the things that covered the time period you're writing for:
+- Progress: anything between a week ago and today
+- Plans: anything from today to the next week
+- Problems: anything between a week ago and today
+
+
+If you don't have access, you can ask the user for things they want to cover. They might also include these things to you directly, in which case you're mostly just formatting for this particular format.
+
+## Workflow
+
+1. **Clarify scope**: Confirm the team name and time period (usually past week for Progress/Problems, next
+week for Plans)
+2. **Gather information**: Use available tools or ask the user directly
+3. **Draft the update**: Follow the strict formatting guidelines
+4. **Review**: Ensure it's concise (30-60 seconds to read) and data-driven
+
+## Formatting
+
+Use this default format unless the user or company supplies another. Pick an emoji that is fun and captures the vibe of the team and update.
+
+[pick an emoji] [Team Name] (Dates Covered, usually a week)
+Progress: [1-3 sentences of content]
+Plans: [1-3 sentences of content]
+Problems: [1-3 sentences of content]
+
+Each section should be no more than 1-3 sentences: clear, to the point. It should be data-driven, and generally include metrics where possible. The tone should be very matter-of-fact, not super prose-heavy.

package/bundled-skills/internal-comms-community/examples/company-newsletter.md

@@ -0,0 +1,66 @@
+<!-- Modified in AAS on 2026-09-05. Audience, permissions and approved sources take precedence over template suggestions; draft only unless sending is authorized. -->
+## Instructions
+You are being asked to write a company-wide newsletter update. You are meant to summarize the past week/month of a company in the form of a newsletter that the entire company will read. It should be maybe ~20-25 bullet points long. It will be sent via Slack and email, so make it consumable for that.
+
+Ideally it includes the following attributes:
+- Lots of links: pulling documents from Google Drive that are very relevant, linking to prominent Slack messages in announce channels and from executives, perhaps referencing emails that went company-wide, highlighting significant things that have happened in the company.
+- Short and to-the-point: each bullet should probably be no longer than ~1-2 sentences
+- Use the "we" tense, as you are part of the company. Many of the bullets should say "we did this" or "we did that"
+
+## Tools to use
+If you have access to the following tools, please try to use them. If not, you can also let the user know directly that their responses would be better if they gave them access.
+
+- Slack: look for messages in channels with lots of people, with lots of reactions or lots of responses within the thread
+- Email: look for things from executives that discuss company-wide announcements
+- Calendar: if there were meetings with large attendee lists, particularly things like All-Hands meetings, big company announcements, etc. If there were documents attached to those meetings, those are great links to include.
+- Documents: if there were new docs published in the last week or two that got a lot of attention, you can link them. These should be things like company-wide vision docs, plans for the upcoming quarter or half, things authored by critical executives, etc.
+- External press: if you see references to articles or press we've received over the past week, that could be really cool too.
+
+If you don't have access to any of these things, you can ask the user for things they want to cover. In this case, you'll mostly just be polishing up and fitting to this format more directly.
+
+## Sections
+Adapt the scope and length to the actual company size; do not assume an employee count. There are a variety of different teams and initiatives going on across the company. To make sure the update works well, try breaking it into sections of similar things. You might break into clusters like {product development, go to market, finance} or {recruiting, execution, vision}, or {external news, internal news} etc. Try to make sure the different areas of the company are highlighted well.
+
+## Prioritization
+Focus on:
+- Company-wide impact (not team-specific details)
+- Announcements from leadership
+- Major milestones and achievements
+- Information that affects most employees
+- External recognition or press
+
+Avoid:
+- Overly granular team updates (save those for 3Ps)
+- Information only relevant to small groups
+- Duplicate information already communicated
+
+## Example Formats
+
+:megaphone: Company Announcements
+- Announcement 1
+- Announcement 2
+- Announcement 3
+
+:dart: Progress on Priorities
+- Area 1
+    - Sub-area 1
+    - Sub-area 2
+    - Sub-area 3
+- Area 2
+    - Sub-area 1
+    - Sub-area 2
+    - Sub-area 3
+- Area 3
+    - Sub-area 1
+    - Sub-area 2
+    - Sub-area 3
+
+:pillar: Leadership Updates
+- Post 1
+- Post 2
+- Post 3
+
+:thread: Social Updates
+- Update 1
+- Update 2
+- Update 3

package/bundled-skills/internal-comms-community/examples/faq-answers.md

@@ -0,0 +1,31 @@
+<!-- Modified in AAS on 2026-09-05. Audience, permissions and approved sources take precedence over template suggestions; draft only unless sending is authorized. -->
+## Instructions
+You are an assistant for answering questions that are being asked across the company. Every week, there are lots of questions that get asked across the company, and your goal is to try to summarize what those questions are. We want our company to be well-informed and on the same page, so your job is to produce a set of frequently asked questions that our employees are asking and attempt to answer them. Your singular job is to do two things:
+
+- Find questions that are big sources of confusion for lots of employees at the company, generally about things that affect a large portion of the employee base
+- Attempt to give a nice summarized answer to that question in order to minimize confusion.
+
+Some examples of areas that may be interesting to folks: recent corporate events (fundraising, new executives, etc.), upcoming launches, hiring progress, changes to vision or focus, etc.
+
+
+## Tools Available
+You should use the company's available tools, where communication and work happens. For most companies, it looks something like this:
+- Slack: questions being asked across the company - it could be questions in response to posts with lots of responses, questions being asked with lots of reactions or thumbs up to show support, or anything else to show that a large number of employees want to ask the same things
+- Email: emails with FAQs written directly in them can be a good source as well
+- Documents: docs in places like Google Drive, linked on calendar events, etc. can also be a good source of FAQs, either directly added or inferred based on the contents of the doc
+
+## Formatting
+The formatting should be pretty basic:
+
+- *Question*: [insert question - 1 sentence]
+- *Answer*: [insert answer - 1-2 sentence]
+
+## Guidance
+Make sure you're being holistic in your questions. Don't focus too much on just the user in question or the team they are a part of, but try to capture the entire company. Try to be as holistic as you can in reading all the tools available, producing responses that are relevant to all at the company.
+
+## Answer Guidelines
+- Base answers on official company communications when possible
+- If information is uncertain, indicate that clearly
+- Link to authoritative sources (docs, announcements, emails)
+- Keep tone professional but approachable
+- Flag if a question requires executive input or official response

package/bundled-skills/internal-comms-community/examples/general-comms.md

@@ -0,0 +1,17 @@
+<!-- Modified in AAS on 2026-09-05. Audience, permissions and approved sources take precedence over template suggestions; draft only unless sending is authorized. -->
+  ## Instructions
+  You are being asked to write internal company communication that doesn't fit into the standard formats (3P
+  updates, newsletters, or FAQs).
+
+  Before proceeding:
+  1. Ask the user about their target audience
+  2. Understand the communication's purpose
+  3. Clarify the desired tone (formal, casual, urgent, informational)
+  4. Confirm any specific formatting requirements
+
+  Use these general principles:
+  - Be clear and concise
+  - Use active voice
+  - Put the most important information first
+  - Include relevant links and references
+  - Match the company's communication style

package/bundled-skills/ios-debugger-agent/SKILL.md

@@ -57,6 +57,12 @@ Use these when asked to inspect or interact with the running app.
 - If the wrong app launches, confirm the scheme and bundle id.
 - If UI elements are not hittable, re-run `describe_ui` after layout changes.
 
+## Example
+
+**User request:**
+
+> Run, debug, or inspect an iOS app on a simulator.
+
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

package/bundled-skills/ios-developer/resources/implementation-playbook.md

@@ -0,0 +1,23 @@
+# Native iOS implementation
+
+## Inputs
+
+Xcode/Swift versions, deployment target, project scheme, feature brief and available simulator/device.
+
+## Procedure
+
+1. Reuse the project's state and navigation architecture. Check API availability against the deployment target before adding platform features.
+2. Implement loading, success, failure and cancellation paths. Keep UI state changes on the appropriate actor and credentials in the project's secure storage abstraction.
+3. Build the actual scheme and test navigation, Dynamic Type, VoiceOver labels and interrupted network requests. State separately which checks used a simulator and which used hardware.
+
+## Worked example
+
+Add a document list with retry. Leaving the screen during loading must not update a disposed view; large text must keep the retry action reachable.
+
+## Verification and handoff
+
+Report the actual files or configuration changed, checks performed, observed results and any untested environment. Keep the original inputs and evidence sufficient to reproduce the conclusion.
+
+## Limitations
+
+Simulator success does not verify signing, push delivery, biometrics or App Store acceptance. Do not upload or distribute without authorization.

package/bundled-skills/issues/SKILL.md

@@ -4,6 +4,7 @@ description: Interact with GitHub issues - create, list, and view issues.
 allowed-tools: Bash(gh *)
 risk: critical
 source: community
+date_added: "2026-09-04"
 metadata:
   author: Shpigford
   version: "1.0"

package/bundled-skills/iterate-pr/SKILL.md

@@ -3,6 +3,7 @@ name: iterate-pr
 description: Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.
 risk: critical
 source: community
+date_added: "2026-09-04"
 ---
 
 # Iterate on PR Until CI Passes