How do I install the Backgroundtasks skill?

Run npx skillmds@latest add caglarbaranbora/backgroundtasks in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Backgroundtasks safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Backgroundtasks?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Backgroundtasks free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Backgroundtasks?

caglarbaranbora (@caglarbaranbora) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Backgroundtasks by caglarbaranbora — Agent Skill

Name: Backgroundtasks
Author: caglarbaranbora

Backgroundtasks

Route BackgroundTasks implementation tasks to the correct Knowledge Contracts -- background task registration and scheduling, task execution and expiration handling, processing task constraints and conditions, and background refresh and widget timeline hookup. Use when registering a task identifier with BGTaskScheduler.register(forTaskWithIdentifier:using:launchHandler:), declaring BGTaskSchedulerPermittedIdentifiers, submitting a BGAppRefreshTaskRequest/BGProcessingTaskRequest, reading earliestBeginDate, handling a BGTask/BGAppRefreshTask/BGProcessingTask in a launch handler, setting expirationHandler, calling setTaskCompleted(success:), setting requiresNetworkConnectivity/requiresExternalPower, or scheduling background refresh that feeds a widget. v1 is BGTaskScheduler-based scheduling and execution only -- no BGContinuedProcessingTask, no legacy Background Fetch (setMinimumBackgroundFetchInterval, performFetchWithCompletionHandler), no unrelated background modes (background audio, background location, VoIP

File contents

BackgroundTasks — Foundations Skill

Purpose

Route BackgroundTasks implementation tasks to the minimum required BackgroundTasks Knowledge Contracts. v1 scope is scheduling and running deferred background work through BGTaskScheduler -- registration, submission, execution, expiration handling, processing constraints, and the hand-off point where background-refreshed data reaches a widget -- not BGContinuedProcessingTask, not legacy Background Fetch, not unrelated background modes, and not URLSession background transfer.

Routing

Load only the contracts relevant to the task. All paths relative to knowledge/backgroundtasks/.

Registering a task identifier with BGTaskScheduler.shared.register(forTaskWithIdentifier:using:launchHandler:); declaring BGTaskSchedulerPermittedIdentifiers; choosing BGAppRefreshTaskRequest vs BGProcessingTaskRequest; submitting with submit(_:); or reasoning about earliestBeginDate -> background-task-registration-and-scheduling.md
Handling the BGTask delivered to a launchHandler (casting to BGAppRefreshTask/BGProcessingTask); setting expirationHandler; calling setTaskCompleted(success:); or re-submitting a request for the next occurrence -> task-execution-and-expiration-handling.md
Setting BGProcessingTaskRequest.requiresNetworkConnectivity/requiresExternalPower; or deciding whether work belongs on BGProcessingTaskRequest versus BGAppRefreshTaskRequest -> processing-task-constraints-and-conditions.md
Scheduling a BGAppRefreshTaskRequest to refresh data a widget depends on, up through the point new data has landed -> background-refresh-and-widget-timeline-hookup.md

Never load more than the contracts relevant to the specific question.

Stop Conditions

Stop and report if the requested topic has no matching Knowledge Contract in knowledge/backgroundtasks/ — do not guess or fall back to general knowledge. BGContinuedProcessingTask (foreground-initiated work that can continue in the background) is out of scope entirely -- newer API surface, deferred, not yet built (see docs/architecture/domain-map.md). Legacy Background Fetch (UIApplication.setMinimumBackgroundFetchInterval, application(_:performFetchWithCompletionHandler:)) is out of scope -- superseded by this framework, not planned as a separate domain; report that explicitly. Other background modes unrelated to BGTaskScheduler (background audio, background location, VoIP push/PushKit) are out of scope entirely. URLSession background transfer configuration (URLSessionConfiguration.background) is networking's job, not this Skill's. Actually calling WidgetCenter.shared.reloadTimelines(ofKind:)/ reloadAllTimelines(), and every rule about the refresh budget governing that call, is widgetkit's job (knowledge.widgetkit.timeline-reloading-and-refresh-budget) -- this Skill only routes to getting the background task registered, submitted, and run so fresh data exists for that call to reload.

---name: backgroundtasksdescription: Route BackgroundTasks implementation tasks to the correct Knowledge Contracts -- background task registration and scheduling, task execution and expiration handling, processing task constraints and conditions, and background refresh and widget timeline hookup. Use when registering a task identifier with BGTaskScheduler.register(forTaskWithIdentifier:using:launchHandler:), declaring BGTaskSchedulerPermittedIdentifiers, submitting a BGAppRefreshTaskRequest/BGProcessingTaskRequest, reading earliestBeginDate, handling a BGTask/BGAppRefreshTask/BGProcessingTask in a launch handler, setting expirationHandler, calling setTaskCompleted(success:), setting requiresNetworkConnectivity/requiresExternalPower, or scheduling background refresh that feeds a widget. v1 is BGTaskScheduler-based scheduling and execution only -- no BGContinuedProcessingTask, no legacy Background Fetch (setMinimumBackgroundFetchInterval, performFetchWithCompletionHandler), no unrelated background modes (background audio, background location, VoIP---# BackgroundTasks — Foundations Skill## PurposeRoute BackgroundTasks implementation tasks to the minimum requiredBackgroundTasks Knowledge Contracts. v1 scope is scheduling and runningdeferred background work through `BGTaskScheduler` -- registration,submission, execution, expiration handling, processing constraints, andthe hand-off point where background-refreshed data reaches a widget --not `BGContinuedProcessingTask`, not legacy Background Fetch, notunrelated background modes, and not `URLSession` background transfer.## RoutingLoad only the contracts relevant to the task. All paths relative toknowledge/backgroundtasks/.- Registering a task identifier with `BGTaskScheduler.shared.register(forTaskWithIdentifier:using:launchHandler:)`; declaring `BGTaskSchedulerPermittedIdentifiers`; choosing `BGAppRefreshTaskRequest` vs `BGProcessingTaskRequest`; submitting with `submit(_:)`; or reasoning about `earliestBeginDate` -> background-task-registration-and-scheduling.md- Handling the `BGTask` delivered to a `launchHandler` (casting to `BGAppRefreshTask`/`BGProcessingTask`); setting `expirationHandler`; calling `setTaskCompleted(success:)`; or re-submitting a request for the next occurrence -> task-execution-and-expiration-handling.md- Setting `BGProcessingTaskRequest.requiresNetworkConnectivity`/`requiresExternalPower`; or deciding whether work belongs on `BGProcessingTaskRequest` versus `BGAppRefreshTaskRequest` -> processing-task-constraints-and-conditions.md- Scheduling a `BGAppRefreshTaskRequest` to refresh data a widget depends on, up through the point new data has landed -> background-refresh-and-widget-timeline-hookup.mdNever load more than the contracts relevant to the specific question.## Stop ConditionsStop and report if the requested topic has no matching KnowledgeContract in knowledge/backgroundtasks/ — do not guess or fall back togeneral knowledge. `BGContinuedProcessingTask` (foreground-initiated workthat can continue in the background) is out of scope entirely -- newerAPI surface, deferred, not yet built (see docs/architecture/domain-map.md).Legacy Background Fetch (`UIApplication.setMinimumBackgroundFetchInterval`,`application(_:performFetchWithCompletionHandler:)`) is out of scope --superseded by this framework, not planned as a separate domain; reportthat explicitly. Other background modes unrelated to `BGTaskScheduler`(background audio, background location, VoIP push/`PushKit`) are out ofscope entirely. `URLSession` background transfer configuration(`URLSessionConfiguration.background`) is `networking`'s job, not thisSkill's. Actually calling `WidgetCenter.shared.reloadTimelines(ofKind:)`/`reloadAllTimelines()`, and every rule about the refresh budget governingthat call, is `widgetkit`'s job (`knowledge.widgetkit.timeline-reloading-and-refresh-budget`)-- this Skill only routes to getting the background task registered,submitted, and run so fresh data exists for that call to reload.

Frequently asked questions